• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 636 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 and project files under Source Control

Franck
Intellectual 685 points

Hello,

I am controlling the files as specified in this page in my source control software:

http://processors.wiki.ti.com/index.php/FAQ_-_CCSv5#Q:_Which_project_files_do_I_need_to_check_into_source_control.3F

My source control software is Perforce, which has the default behavior to put all files with "read-only" attribute when they are not checked-out. Unlike CCSv4, I get some strange behaviors in CCSv5 that I would like to clarify:

1- Each time I try to import a project in CCSv5, it asks me if I want to remove the "read-only" attribute on the ".cproject" file (my file is read-only when not checked-out in Perforce). If I check-out the file and answer "yes", it looks like nothing changed in the file after import is complete. If I answer "no", the project seems to import correctly. Is it ok if I answer "no" or there is some side-effects I don't see? If nothing changes in that file anyway, why is the importing process requesting to remove the read-only attribute?

2- Sometimes when I try to import a project, the same thing happens with the ".settings/org.eclipse.core.resources.prefs" file. Unlike the ".cproject" file, changes happen in that file. Here is an example:

before:

#Thu Mar 01 12:04:55 EST 2012
eclipse.preferences.version=1
encoding//Release_53A0010/Cfg/subdir_rules.mk=UTF-8
(...)

after:

#Thu Mar 01 14:07:34 EST 2012
eclipse.preferences.version=1
encoding//Debug_53A0010/Cfg/subdir_rules.mk=UTF-8
(...)
encoding//Release_53A0010/Cfg/subdir_rules.mk=UTF-8
(...)

Does this file really need to be put under source control since additional lines are added over time depending on the target build machines the project is imported?

Thanks

Franck

  • 0
    TI__Guru**** 173310 points

    Hi Franck,

    There is a known bug in CCS 5.1.0 (which is due to an Eclipse bug) where the .cproject or .project files get touched frequently, trigerring those messages you are seeing. CCS 5.1.1 contains a workaround for it, and a permanent fix has been contributed to open source and will appear in CCS 5.3. 

    If you could upgrade to 5.1.1 and open a new workspace and import your project into it, that should help with the problem. This step is necessary mostly to ensure that the project gets “migrated” to the newer version of CCS.  

    If you do plan to upgrade to 5.1.1, one thing I wanted to point out is that if you originally installed 5.1.0 with the web installer then there are some known issues with updating to 5.1.1 via CCS Update manager, which we are actively working on addressing. Hence I would not advise this update method at this time. Instead please download the full installer for 5.1.1 and you may install on top of your existing 5.1.0 installation. Download and more info is here: http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_5_Downloads

    There is also still a known bug where CCS files like .ccxml and project files should be automatically checked out when changes are necessary to be made just like for other files. This still needs to be fixed and is being tracked in bug # SDSCM00043340. 

    Hope this helps clarify things.