Message Edited by Bruce_ on 2007-02-1812:18 PM
tHello,
I found this old thread through a Google search of "Subversion Code Warrior".
Has it YET occured to anyone , 3 years later, to STOP SCREWING WITH THE .mcp file?
What even changes there for just opening the project, anyway? There is no good way to insure multiple users (or even one, for that matter), don't either save it when they shouldn't or not save it when they should. This circumvents completely the purpose of using source control software in the first place.
Any change there could make creating an exact - match target impossible.
Is it at least true that the only changes that SHOULD be there are through the project "Settings" interface? So the rule can at least be, "IF and ONLY IF you change something through the "Settings" dialog, then save the .mcp file?
I have had "read-only" set before, and when opening the project been warned "The settings file for project "...mcp" was locked, so some user settings will not be saved". This is a real nuisance - but does it solve the problem? Just "click - through" each time. Will anything important be lost this way, without knowing it?
If nothing significant is stuck into the .mcp file casually, wouldn't a simple bug fix patch to remove the willy-nilly stuff solve a large hastle for everyone?
Thanks.
Hello
CodeWarrior also stores some internal data in the .mcp file.
If you are planning to use a version control software I would highly recommend you to export your .mcp file to a .xml file and checking the .xml file in your version control system.
Any programmer who checks the project out should then import the .xml file to create a .mcp file.
CrasyCat
CrasyCat wrote:
.... I would highly recommend you to export your .mcp file to a .xml file ....
Could you please explain how to do that ?
Hello
- Start CodeWarrior
- Open your .mcp file in the IDE
- Select "File" -> "Export Project" and follow the instructions on the screen.
CrasyCat
Ah, thanks !
For some strange reason i have always overlooked that :-/