meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
programming:c:ceedling [2021/04/22 11:10] – niziak | programming:c:ceedling [2021/04/22 12:52] – 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 '' |
<code c> | <code c> | ||
TEST_FILE(" | TEST_FILE(" | ||
Line 14: | Line 14: | ||
All dependent includes needs to be added manually in test '' | All dependent includes needs to be added manually in test '' | ||
- | To automatically add linked resources there is a project option: | + | This is desired behavior because '' |
+ | Perhaps you should break dependency chain by including mocked header. | ||
+ | |||
+ | <code c> | ||
+ | # This will include 20 another headers :) | ||
+ | |||
+ | #include " | ||
+ | |||
+ | # To prevent this: | ||
+ | #include " | ||
+ | </ | ||
+ | |||
+ | ===== extern keyword ===== | ||
+ | < | ||
+ | WARNING: No function prototypes found! | ||
+ | </ | ||
+ | By default '' | ||
<code yaml> | <code yaml> | ||
- | :project: | + | :cmock: |
- | :auto_link_deep_dependencies: TRUE | + | :treat_externs: :include |
</ | </ | ||
- | But it has impact on performance. | ||
+ | ===== volatile function parameters ===== | ||
+ | <code c> | ||
+ | void myfn(custom_t *m, volatile uint32_t *var); | ||
+ | |||
+ | error: conflicting types for ... | ||
+ | </ | ||
+ | |||
+ | [[https:// | ||
+ | The C99 standard recommends against using volatile as function call parameters and as return values, | ||
+ | stating that it is undefined behavior (because it is implementation- | ||
+ | not be depended upon. | ||
+ | * **Workaround1: | ||
+ | * **Workaround2: | ||