- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi
I have a ccs5.1 project for my cortex m4f development ( originally created under ccs4 early this year.) . I have the .project and .settings files checked into source control (clearCase). It seems that these files saved my compiler and linked settings such as options, header-include paths, lib path etc. Whenever I import the projects to my workspace, it automatically generates the .cproject for me. The CCS project property displays all of those compiler settings as well. We are ok with it for months until I recently found that after I added a new include path and it is saved to .cproject only.
Now, without the .cproject, the CCS is opened with all of the old good settings except the newly added header-include-path. If I keep the .cproject in the project, then it opens with all of the information.
So, I am confused with why my .project file worked for me for so long and it remembers so many old settings but not new ones. Are there any hidden places that store these configurations?
Thanks
Eric
