• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 704 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.

Unwanted .project file modifications in CCS5.1.0.06000

gbl
Intellectual 400 points

Since CCS5.1.0.06000 there is an unwanted effect: the .project file contains the name of the last generated output file (either none or a combination of configuration name/path and output file name).

.project is modified after each modification (is empty after importing projects and contains the latest configuration/output name after a build). This is extremely disturbing in a version control system based environment: although no real changes in .project are made, just for updating the output file name .project is checked out and thus recognizing newer versions of .project is blocked.

I guess this is based to some Eclipse 'improvements' which found their way to CCS5.1.0.06000. There was a similar problem several versions ago which was solved by TI (don't touch .project for such modifications).

Is there a way to restore the pre-CCS5.1.0.06000 behavior in this point?

  • 0
    TI__Guru**** 484071 points

    Hello,

    What version of CCSv5 where you using before 5.1.0.06000 (where there was no issue)? Were you on 5.1.0.05000? I'm just trying to determine which pre-release this functionality was introduced.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 400 points

    yes, I used 5.1.0.05000. There are other heavy drawbacks with 5.1.0.06000 when importing projects. I will open a separate thread for that.

  • 0 in reply to gbl
    TI__Genius 9435 points

    What types of modifications cause the .project to be modified for you?  I see that an imported project's .project file is modified only during the first build.  After that, subsequent builds don't modify the .project file anymore.

    There still is one known issue where both the .cproject and the .project files are touched when you change the active build-configuration.  This CDT problem is tracked in https://bugs.eclipse.org/bugs/show_bug.cgi?id=340219.  On our side, we're tracking this problem in SDSCM00039515 [CDT] switching active build configuration touches .cproject file.  There is no guarantee that this can be addressed in CCSv5.1.0 timeframe.

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Intellectual 400 points

    Starting with 5.1.0.06000 the output file (.out or .lib) become part of the project. Whenever a project is cleaned the project file is modified (because the output files are deleted), whenever a project is built the project file is modified (because the output files just built are added). So there is no way to have a non-modified version in a version control system - it is always automatically checked out due to those modifications.

    Problem is: if you want to look at the latest project file but have for the reasons mentioned above checked out the project file, you will not see the latest one.

    This was much easier with 5.1.0.05000 and before.

  • 0 in reply to gbl
    TI__Genius 9435 points

    I don't see the behaviour you're describing in build 06000.  For me, the .project file's timestamp does not change on build/clean.  Only on active-configuration change.

    I've tried building/cleaning from the IDE.  Are you building from command-line?

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Intellectual 400 points

    We are at least sometimes building from command line and, probably important, for several configurations. That probably causes the problems (sounds similar to what you mention when you change the active configuration).

    Is there a special reason that the generated files now are part of .project while they were not until now?