 Storing language.settings.xml in a VCS [message #1303960] |
Sat, 19 April 2014 15:35  |
 Steven Soloff
Messages: 3
Registered: April 2014 |
Junior Member |
|
|
(Kepler SR2)
Hi All,
My team recently needed to customize the CDT GCC Built-in Compiler Settings MinGW provider "Command to get compiler specs". In order for this command to be shared among all developers, we unchecked the "Use global provider shared between projects" option so that the relevant configuration will be stored in the .settings/language.settings.xml file, which we then committed to our VCS.
Unfortunately, the corresponding node in language.settings.xml where this information is stored also has an attribute named "env-hash". This value appears to be dependent on the details of the toolchain discovered by the CDT. Specifically, if the toolchain on one developer's machine is installed to a different location than the toolchain on another developer's machine (even if the toolchains are otherwise identical), env-hash is updated, and language.settings.xml appears to be in a modified state to the VCS client.
(If we check "Store entries in project settings folder (easing project migration)", we observe the discovered include paths to the toolchain location under the same node in language.settings.xml, thus suggesting that the toolchain location is indeed relevant to the calculation of env-hash. We also tried changing those paths to make use of environment variables that are common to every developer's setup [e.g. use "${MINGW_HOME}/include" instead of "C:/MinGW/include" as written by CDT]. While CDT seems to read that modified configuration and expand the environment variables correctly, it still writes back out the absolute paths, thus once again modifying the file.)
In general, is it acceptable for language.settings.xml to be stored in a VCS? If so, is there a way to prevent env-hash from being updated so that language.settings.xml doesn't appear to be modified in everyone's working copy (except for the last developer to commit it)? If not, is there an alternate mechanism for sharing language settings provider options among the team in a VCS?
Thanks,
Steve
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02327 seconds
] 
Search
Help
Register
Login
Home
