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

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.

CCSv5/CCSv6 Preprocessor Output

user1515739
Prodigy 20 points


I'm debugging a complex macro and I just can't find a way to see what the preprocessor is producing. All the references I find say "oh, just enable -ppd or -ppi or -ppo and look at the .pp file." Problem is, for every combination of those options all I see in the .pp file is the list of included files with their paths. No code. No comments. No macro expansion results.

I've tried all the same set of experiments in both CCSv5 and CCSv6.

I must be doing something bonehead but I'll be darned if I can figure out what step I missed. 

Any help would be greatly appreciated.

  • 0
    TI__Guru**** 171349 points

    Hi,

    When you use these options, the .pp file is actually in the same directory as the source file. What you are probably opening is the .pp file automatically generated by CCS in the output build directory (Debug, Release or whatever you named it).

    The file above was produced when I enabled the option -ppc, and yielded the attached result below (the original .c file also follows attached)

    2350.blinky.zip

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 20 points
    thanks, Rafael. this is exactly what i was doing wrong. kind of a bad design to have .pp mean totally different things though, doncha think?
  • 0 in reply to user1515739
    TI__Guru**** 171349 points

    Well, it is a Catch-22 scenario. Our compilers used .pp extensions for years (decades?) before we adopted Eclipse as our main IDE. Eclipse chose this extension and we can't change this and risk breaking compatibility with other things...

    (edit) I had the impression this is coming from Eclipse, but there is a possibility this is a feature of CCS itself. More investigation is being done, but a bug number SDSCM00052462 was already filed to address that (you can check its status in the link SDOWP in my signature below).