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/TM4C1290NCZAD: #ifndef bracketing in include files is not working.

Part Number: TM4C1290NCZAD

Tool/software: Code Composer Studio

I just recently upgraded from CCS7 to CCS8.  Deleted my entire old installation, and reinstalled.  I'm now on compiler version TI v18.1.3.LTS, but seem to have problems with the compiler.

1. my include files are bracketed with #ifndef ... #endif blocks to prevent re-definitions by accident.  It seems that the compiler is completely ignoring them, both in my software, as well as all the TI system software (which is producing hundreds of errors and warnings).

2. I'm using TIRTOS in this application, and it seems the compiler's include files and the ndk include files are in conflict.  The compiler is seeming to do a pretty bad job on this.

3. The new compiler seems to be unable to handle variable declarations inside blocks.  for instance 'for(int I=0; I<100;i++)' produces an error, until I move the declaration out of the for definition, and to the top of the function block.

I'm currently working on reinstalling the older version of software, to see if I can get back functional again.

  • What version of the compiler did you use before?  

    David Dudley said:
    for instance 'for(int I=0; I<100;i++)' produces an error

    I have to use the option --c99 to get this to build clean.  I tried a few different versions of the compiler.  All of them require the option --c99.  

    As for your other problems ... Your descriptions are too vague to act on. Something goes wrong while preprocessing.  A good way to debug such problems is to build with the option --gen_preprocessor_listing, then inspect the resulting .rl file.  Please read more about that option in the ARM compiler manual.

    Thanks and regards,

    -George

  • Since it has been a while, I presume you resolved your problem by debugging it with help from the option --gen_preprocessor_listing.  If that is not the case, please let us know what happened.

    Thanks and regards,

    -George