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.

CCS/CCSTUDIO-C2000: Is it possible to build the same image file between CCSV4 and CCSV7

Part Number: CCSTUDIO-C2000
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hello there,

I've been trying to define a ccsCompiler.opt file similar to the "ccsCompiler.txt" that was posted here that contains the include paths and other compiler options.

Base on I've tried so far it seems that the paths have to be declared as absolute paths in the ccsCompiler.opt file otherwise the project does not build.

My question is if there is a way to declare paths using either project path variables or project relative paths?

Thanks a lot,

Doru

  • Hello Doru,

    your post topic: Is it possible to build the same image file between CCSV4 and CCSV7
    A: Probably it is possible. However, I see no practical sense to generate the same image by two CCS generation.

    Q: My question is if there is a way to declare paths using either project path variables or project relative paths?
    A: YES, in case of CCS 8.x, 7.x and 6.x.
  • Hello Tomasz,

    Thanks for taking your time to reply to my post. However the question that I posted was about defining relative paths in a ccsCompiler.opt file that can be passed to the compiler with the "--cmd_file=ccsCompiler.opt" option.

    You are right that using the Code Composer Studio we can specify include paths using the "PROJECT_LOC", "CCS_BASE_ROOT" or other path variables but the problem that I have is declaring relative paths in a compiler command file. There are few examples of "ccsCompiler.opt" in the C2000Ware and all of them use absolute paths and I am hoping that it is possible to use relative paths to header files as each developer uses its own root for the workspace.

    The reason I want to use compiler command files is because it is a lot easier to maintain a text file (as the compiler command file) than the ".project", ".cproject" files used by CCS.

    Thanks again,

    Doru

  • Doru,

    The compiler options file that you pass to the compiler via --cmd_file does not support the use of CCS variables like PROJECT_LOC etc. So you cannot add paths in that file that are relative to a variable. An alternate way to handle this that may be helpful is discussed in this forum thread

    You should also be able to use relative paths without the use of variables, but note that when building in CCS, the current directory is the build configuration directory (like Debug or Release) so paths should be relative to that directory.