Reputation: 26333
Using Tortoise-svn with C++ VS2010 project. I would like to know in which cases you are to commit .sln file.
Some reasons I see for commiting .sln file:
What other reasons for commiting .sln ? How would .sln be merged ?
Also, who is generating .sln file ? Is it generated at each qmake_all (or make_all) ?
EDIT
I am using Tortoise SVN GUI. It should tell me when .sln has been changed by me.
Now, under which circomstances is .sln changed ?
And also: how are .sln merged ?
More pragmatically, in which case should I do accept mine or accept theirs for .sln when I just updated ?
EDIT
When/How is .sln produced from .pro file ?
EDIT
To make part of my question clearer:
after an update with tortoise svn, if .sln is conflicted, should i
thanks!
Upvotes: 1
Views: 226
Reputation: 4319
As for me you do not have needs to store sln file, because sln file is derivative from your pro file (in other words sln is generated from pro file), so consider to storage only primary project definition file (this is a pro file) and omit generated artifacts. The primary reason is when you decide to change developer environment (for example it can be mingw) you can do it in the moment with pro file, and spend a lot of time for converting sln file.
Upvotes: 2
Reputation: 7919
Usually any svn GUI like TutoiseSVN will detect any changes in the solution file and will warn you to commit .sln file as well but if you are not using such a GUI, then you can find related solution parameters by opening .sln file with a text editor like Notepad++ and you can see all the variables about your project
Upvotes: 0