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.

CCSv4: (v4.1.3) multiple projects for production build and unit test

Hi

When we used CCSv3, we were able to have one main project for the production build, and several projects in lower level folders to unit test various modules. I tried doing this in ccsV4, but the main project at the highest folder level wants to include the .cfg output of the lower level unit test projects. Having to manually exclude the test.c files was also a pain.

So then I tried putting the test projects at the folder level equal to the main build project and link in the files I need. This worked well now that the main project didn't see the .cfg files and I didn't have to exclude test.c files. But the problem I have is when these projects are imported into another PC where the root directory is not the same. It appears that when I linked files to the test project, eclipse used an absolute link address to the file instead of a relative. To get the test builds to work, I have to re-link all the files. Not!

Is there a way to get CCSv4 to use relative addresses when linking files to a project?

Or maybe there is a better way for me to setup our main build an unit test projects?

Cheers

 

  • Thanks to my co-worker, the solution may be in

    http://processors.wiki.ti.com/index.php/Portable_Projects

    What worked was creating a macros.ini file with this in it

    TEST_SRIO_PATH_VARIABLE=..\

    and then changing the absolute addresses in the .pjt from this

                <location>d:/views/workspace1/EVM6472/Common.cluster/ErrorMgr.module/src/ErrorMgr.c</location>

    to this

                <location>TEST_SRIO_PATH_VARIABLE/EVM6472/Common.cluster/ErrorMgr.module/src/ErrorMgr.c</location>