meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
programming:c:ceedling [2021/04/22 11:10] – niziakprogramming:c:ceedling [2021/04/22 12:02] – niziak
Line 4: Line 4:
 ===== add .c file  ===== ===== add .c file  =====
  
-When ceedling fails to pickup automatically .c file it can be added to given test by+When ''ceedling'' fails to pickup automatically .c file it can be added to given test by
 <code c> <code c>
 TEST_FILE("source_file_to_compile.c") TEST_FILE("source_file_to_compile.c")
Line 14: Line 14:
 All dependent includes needs to be added manually in test ''.c'' file. All dependent includes needs to be added manually in test ''.c'' file.
  
-To automatically add linked resources there is a project option: +This is desired behavior because ''ceedling'' gives you control how to treat additional dependeny headers.  
-<code yaml> +Perhaps you should break dependency chain by including mocked header. 
-:project: + 
- :auto_link_deep_dependencies: TRUE+<code c> 
 +# This will include 20 another headers :) 
 + 
 +#include "cpu_hal.h" 
 + 
 +# To prevent this: 
 +#include "mock_cpu_hal.h
 </code> </code>
  
-But it has impact on performance.+