You would think with the uVision's Run-Time Environment Manager and Software Package Selector with all its version control and download features that I should have no trouble switching between machines while working on a project. Well, you'd be wrong.
Half the files in my project are just being referenced to locations in the Keil program directory, while the other half are copied to my project folder. Why?
Some of these files are considered Packages, some are considered Components, and some are just considered included files. They are all just .c and .h files. Why are some handled one way, and others handled differently?
Why after moving my project to a new system do I have to spend hours making sure every setting in every menu is identical to the other machine my code was created just to get the code to compile when all of the information needed to do this already is (or should be) stored in the project file?
Unless I'm missing something all I see from these 'features' is larger file sizes for data that isn't actually being used to do anything to help workflow. All I'm finding are obstacles and reasons to switch to another IDE.
You mean "eg" not "ie": SVN is just one example of an SVCS (Software Version Control System) - it is not a synonym for "SVCS".
As has been discussed before, the trouble with trying to keep a uVision project under Revision Control is that it "pollutes" the project files with a lot of irrelevant stuff - so the SVCS reports them as "changed" even when no real modifications have been made!
:-(
Simply opening a project to view, then closing it without making any edits or changes can result in the Project files being marked as "Dirty".
http://www.keil.com/forum/59513/
Sigh.
A pedant might start questioning whether it is "eg" or "e.g.", "ie" or "i.e.".
But life's too short to debate with self appointed forum police.
So I didn't do that - just the significant point that it is an example and not a synonym.
but you choose to focus on that rather than the issues of trying to use a SVCS on a uVision project ...
Have you seen this application note and example?
http://www.keil.com/appnotes/docs/apnt_279.asp
On page 5 of the note it states: ========
Note: The project files uvprojx and uvoptx have UNIX-style line endings (LF). In Windows systems, usually CRLF is used. Git automatically detects this and changes the line endings to CRLF on the server. But then the status of these two project files is always “changed”. You can get around this problem using the command git config --global core.autocrlf false ==============
You may be able to make these changes, so the version control works properly.