Mark VanderVoord

Hi @lafonso-gnrc -- yes, some of the features have had their name change between 0.32 and 1.0.n. This includes replacing the old `use_preprocessor_directives` with more complete preprocessing handling using `use_test_preprocessor`....

Hi. Looking in your project.yml file, I see that you're using the `gem` version of ceedling for most of the operation (which I believe you've mentioned is 1.0). The dependencies...

Hi! You can adjust the verbosity from the default by specifying `-v=2` or `--verbosity=warnings`. - 0 -- Silent - 1 -- Errors - 2 -- Warnings - 3 -- Normal...

Both of these topics are definitely issues. I believe they both exist in at least one open GitHub Issue each? In any case, it's a feature that was implemented poorly...

Can you more thoroughly describe what doesn't work about it? Are you getting an error? What step is failing?

Thanks for digging into this, folks. Am I understanding correctly that, while relative header files are still working properly, Ceedling is no longer identifying the corresponding C file and automatically...

Unless I'm misunderstanding: the normal usage of a relative header file is to find a header relative to the current C file and to use it during compilation. That's working....

:) What you are describing here is very close to how `scalpel` works, which is a new CMock feature. It's currently under development, but likely going to be the release...

Sadly at the moment it exists only as a collection of files on my personal repo. It's staged to get added to the next release when some things are worked...

Not that I am aware of. As far as I know, we'd be the first... and that makes me excited to work on it. :)