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/TMS320F28022: Auto save .h files?

Part Number: TMS320F28022

Tool/software: Code Composer Studio

I noticed this in CCS 6, and I was kinda hoping CCS8 would have fixed it.

If I edit a .c file and a .h file, then click the "build all" hammer, only the .c file gets auto saved.

Since the .h file doesn't, inevitably there are compile errors and I need to do again.

Is there a setting to tell CCS to include the .h files in the auto save sequence.

Thanks, Mark.

PS. I do have the 'Preferences->General->Workspace->Save automatically before build' checked.

  • Mark,

    I believe what is happening is that the .h files are not in the project.

    For example here I have 3 files open in the editor.  All 3 are used by a project.  I dirty all 3 (note the *)

    I then build the project.  You can see that the first 2 got saved but not the last one:

    The difference between splash_image.h and grlib.h is that the first is in my project and the second is only referenced via a #include.

    If I add a reference to grlib to my project, note the little shortcut arrow on top of the file icon.  i.e. I didn't copy the file into the project just made a reference to it.

    Now if I open the file and dirty it:

    And then build:

    It saves the file.

    To me it seems to treat the files that you have in the project as managed.  But for those that are outside of the project it does not save those automatically.  So if there are files that I am really owning then I either copy them into the project or if they are shared files I add a reference/link to them in the project.  When you select to add a file to a project either via the add files menu or by dragging in a file it will give you the option to copy it or link it.

    Regards,

    John

  • Yes, John, you are correct, the .h files are in the include folder and not specifically included in the project. The are found during compile via the -i search path.

    What you say makes sense. I will test it, but I can see already that is what is going on.

    Since I don't want to clutter my project with endless .h files (I have many) I will leave them where they are and live with the issue.

    Thanks for taking the time on this.

    Mark.