• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 625 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

.cproject version control

Roman Karlstetter
Intellectual 560 points

Hi,

this is more a feature request than a question. At the moment, it's very hard to merge two versions of a .cproject file, as one change in the configuration (e.g. compiler version) changes multiple xml-tags of the configuration-file in a not very obvious way.

What are the reasons behind this strange configuration-file update behaviour? Are there any plans to do this in another way such that only one tag (the one containing the compiler version if we take the example from above) is changed?


Kind regards,

Roman

  • 0
    TI__Guru**** 450911 points

    Hi Roman,

    The information in the .cproject is for project settings contributed by CDT. It is unlikely we will change this behavior since that file format is something we inherit by leveraging Eclipse CDT ( we (CCS team) does not own this particular feature).

    ki

  • 0 in reply to Ki
    Intellectual 560 points

    Hi Ki,

    thanks for these insights.

    I do understand that you won't change features provided by CDT. But, on the other hand, if this feature is provided by CDT, I'm wondering even more which the behaviour is like it is, because changing single tags is no problem for standard C++ projects. This is the case even inside CCSv6, so might there be perhaps a problem in how CCS-projects use this feature of CDT?

    Best,

    Roman