This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
This may be a niche situation that doesn't have an answer, but I'll try anyway.
When function testing my low level code, I have typically developed my "unit test" projects with multiple source files of similar group (all the UTIL files, for example) and the corresponding unit test files.
To build and test on target, I would exclude all but the source file and corresponding unit test file (and unit test main/assert files), build, run on target, and capture the test output.
When I want to test another file, I would exclude the first source and test files (util_crc.c and ut_utils_crc.c for example) and include the new files under test (utils_ring.c and ut_utils_ring.c), build, run on target, and capture the test output.
I'm trying to build up to a proper automation setup now, maybe for a weekly build server or such, and have been experimenting with the command line options.
First question, is there a command line equivalent for this exclude/include operation on the ccs project?
Secondly, maybe I'm going down the wrong path. Is there another project style/method I should be considering for this multiple independent file builds testing I do?
Thanks for any advice,
Neal
HI Neal,
First question, is there a command line equivalent for this exclude/include operation on the ccs project?
Not for existing projects.
Secondly, maybe I'm going down the wrong path. Is there another project style/method I should be considering for this multiple independent file builds testing I do?
A better approach would be to have an existing project with multiple build configurations:
Each build configuration would have the files that correspond to a specific unit test. The other files would be excluded from the build. Then when you wish to build for a specific test, you just build that build configuration. No need to constantly exclude/include files for the build but instead you just select the relevant build configuration.
Thanks
ki
Are there command line options for creating new build configurations, out of curiosity?
Are there command line options for creating new build configurations, out of curiosity?
Only when creating a new project. Not for existing projects.