• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 32 subscribers
  • Views 219 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.

CCS/TM4C1294NCPDT: CCS project file check-in

Harshel
Intellectual 955 points
Part Number: TM4C1294NCPDT


Tool/software: Code Composer Studio

Hi,

I am developing application using TM4C1294NCPDT, TI-RTOS and CCS v9.0.1.

I have referred following link: "https://software-dl.ti.com/ccs/esd/documents/sdto_ccs_source-control.html". 

I would like to know about ".settings" folder which is created with project.

I found following files "org.eclipse.cdt.codan.core.prefs", "org.eclipse.cdt.debug.core.prefs" and "org.eclipse.core.resources.prefs" are generated.

1. Which project properties are stored in each files ?

2. Do I need to check-in to repository ?

3. What will happen if I didn't check-in ?

 

File "makefile.defs" is also created.

1. What additional make file rules are stored ?

2. Do I need to check-in to repository ?

3. What will happen if I didn't check-in ?

 

Provide any example and/or suggestion which I can try and understand importance ?

Please provide more specific details about these with reference to CCS.

Thanking you.

Best Regards,

Harshel

  • 0
    TI__Guru**** 173310 points

    Harshel,

    Harshel said:
    I found following files "org.eclipse.cdt.codan.core.prefs", "org.eclipse.cdt.debug.core.prefs" and "org.eclipse.core.resources.prefs" are generated.

    These files are part of standard Eclipse that CCS is based on. It contains information on custom Eclipse/CDT settings applied to the project. For a bit more information on what it stores, please see this post. 

    Yes, you should check in the .settings directory along with all the files inside it.

    Harshel said:
    File "makefile.defs" is also created.

    makefile.defs has additional make rules for TI-RTOS projects. You can take a look at the file in one of the TI-RTOS example projects to have an idea about its contents. 

  • 0 in reply to AartiG
    Intellectual 955 points

    Hi,

    I observed that if I have only files ".ccsproject", ".cproject", ".project", "GPIO_Pos_Sw.cfg" and "tm4c1294ncpdt.cmd" in project folder.

    Tried to load project with these files, it is imported successfully. Other folder and files such as ".settings", etc. are generated.

    I compiled and downloaded hex file successfully. It's working fine.

    Is it OK if I check-in ".ccsproject", ".cproject", ".project", "GPIO_Pos_Sw.cfg" and "tm4c1294ncpdt.cmd" these files ?

    Any suggestion or improvements for this trial.

    Best Regards,

    Harshel

  • 0 in reply to Harshel
    TI__Guru**** 472161 points

    Hello Harshel,

    Harshel said:
    I observed that if I have only files ".ccsproject", ".cproject", ".project", "GPIO_Pos_Sw.cfg" and "tm4c1294ncpdt.cmd" in project folder.

    Yes those are all critical files. I assume your actual source files are linked in from a location outside the project folder.

    You may lose the custom eclipse settings mentioned in Aarti's post if you do not check in the contents of the .settings folder.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 955 points

    Hi,

    I am analyzing with some trials. I found that settings related to CCS are particularly store in ".settings".

    Arti's post confirms that settings made "Preference", breakpoints used during debug and   are stored in .settings.

    Also I found that only "Preference" are important to check in if we are using customized settings. Other settings are re-generated while importing/loading project.

     

    Sample projects provided with SDK contains .settings folder with only file "org.eclipse.cdt.codan.core.prefs".

    As of now I have concluded that minimal project files required are ".ccsproject", ".cproject", ".project", "GPIO_Pos_Sw.cfg" and "tm4c1294ncpdt.cmd" for successful compilation.

    Best Regards,

    Harshel