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.

CCSTUDIO: Is it possible to create an additional configuration in a CCS project that is not a cross compiler?

Part Number: CCSTUDIO

I'm using Windows, and i have already installed MinGW, CCS also have found that. I'd like to create a new configuration to my embedded project, but for unit testing, so i'd use plain GCC. A simple makefile configuration would be enough as well. But when i'm adding a new build configuration to my CCS project, despite i can choose the GNU (MinGW) compiler, it wants to use the msp linker as well. Can i create somehow a project to fulfill my purpose, or do i have to just place my test files in the project, exclude them from the main build, and compile the tests from cli with an additional Makefile?

Thanks in advance!

  • Hi Edvin, I have referred your question to the topic matter expert.

  • Edvin,

    A standard CCS project does not support this.  However you could create a "C/C++ Project" that uses the Eclipse/CDT project system.  This would enable you to create a project that uses GCC for your PC.  I am not an expert on this but here are some basic instructions.

    From the File menu select New -> Other and then under C/C++ select C/C++ Project

    On the next screen you will be able to select GCC for your host (in my case I am running on a mac).

    So in this scenario you would have 1 project targeting your embedded device and one for the PC.  You can share source code between them.

    Regards,

    John

  • John,

    Thank you for making clear that CCS projects don't support build configurations for regular build procedures!

    Since I already had a makefile, my soultion was the following: Inside of my test directory in the CCS project, I created a C/C++ project, and selected "Makefile Project with Existing Code". The trick was to not select any toolchain, because selecting one would disable the option to use an external builder and in that case we couldn't use our prepared Makefile.

    Thanks again,

    Edvin