• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 522 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Access to Predefined Symbols and Compiler Options from Post-build Step Batch File

Tony Morrell
Genius 4130 points

Hi,

CCS 4.1.2.00027

I am running a post build batch file from which I would like to determine the predefined symbols I have defined for the build (Tool Settings/TMS470 Compiler/Predefined Symbols "--define, -D").

I would also like to access the compiler options (as displayed under Tool Settings/TMS470 Compiler "All options" field.

I'm sure this is possible, I just can't find out how.

All help gratefully appreciated.

Tony.

 

 

 

 

  • 0
    TI__Expert 4280 points

    My understanding is that you want your batch job to be able access the settings (including the -D values) that are selected in your CCS project.  I do not know how to do that or if it is possible.  Hopefully some CCS guru can help you out.

    Perhaps the following may be of some use if there is not something more direct that can be done.  Using -ppm and -ppa on some file, foo.c, in the build will produce a file, foo.pp, that will contain #defines for all of the defined macro symbols in the compilation of foo.c, including those created with -D.  (The -ppa just says to continue compiling after producing the .pp file.)  This would be a hard way to get at the information you want, but I thought I would pass it along in case it is of any use.

     

     

  • 0
    TI__Guru**** 173310 points

    Tony,

    Within your CCS project folder, under the \Debug sub-folder (or whatever the name of your build configuration is), the files subdir.mk and makefile contain the compiler and linker command lines as it is passed to CCS. You could probably parse these files to extract the information you are interested in as part of the post-build steps.

  • 0 in reply to AartiG
    Genius 4130 points

    Thanks Aarti, this seems like the best option. Regards, Tony.