<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>how to put uVision project files under source control</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/26484/how-to-put-uvision-project-files-under-source-control</link><description> 
Hello, 

 
has anybody a good solution how to put the uVision project files
under source control? 
We only want to store the information that is absolutely neccessary
to rebuild the objects. We do not need 
informations how windows are placed - since</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/139406?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 16:03:58 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:2e548cd4-8732-4e97-9fe0-baee8b29ba21</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
No, that is not the case!&lt;/p&gt;

&lt;p&gt;
The project files are updated immediately the change is made.&lt;/p&gt;

&lt;p&gt;
IMO, this is a very &lt;i&gt;&lt;b&gt;BAD&lt;/b&gt;&lt;/i&gt; feature - because it means
that there is no way to discard changes made to the project!!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/130561?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 15:01:54 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a297ff2e-07e5-41b1-869a-11a1fe11d426</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;No, this has nothing to do with building!&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
True, but that is not what I meant: I was under the impression
that project files are saved only after closing a project. thus, if
one creates dependencies into C modules that are not part of the
project files when the check-in is done, there is a problem.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/125871?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 14:38:13 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:32f5dd15-b7a9-43cf-814e-aeb7a1d57992</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
No, this has nothing to do with building!&lt;/p&gt;

&lt;p&gt;
The &lt;b&gt;.opt&lt;/b&gt; file records what files were open, and the
positions of their windows.&lt;/p&gt;

&lt;p&gt;
The &lt;b&gt;.uv2&lt;/b&gt; file can use relative paths, so the project
doesn&amp;#39;t have to be always checked-out to an identical path, but the
&lt;b&gt;.opt&lt;/b&gt; file uses fully-qualified paths - so if someone checks
the project out to a different path, you get a &amp;quot;cannot find file&amp;quot;
message for each window it tries tp re-open.&lt;br /&gt;
But this doesn&amp;#39;t affect building - only the attempt to &amp;quot;re-open&amp;quot; the
files that were last open.&lt;/p&gt;

&lt;p&gt;
Hence, of course, if there are no files open when you check-in,
the problem doesn&amp;#39;t arise!&lt;/p&gt;

&lt;p&gt;
Note that I never use the &amp;quot;integrated&amp;quot; source control - I always
keep it separate.&lt;br /&gt;
Dunno if that has any effect...?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/103610?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 12:59:22 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:6e01bb67-8f36-45c3-9821-d7fa21e70e92</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
UV2 &amp;amp; UV3 were the same; UV4 is different...&lt;/p&gt;

&lt;p&gt;
See: &lt;a href="http://www.keil.com/support/man/docs/uv4/uv4_b_filetypes.htm"&gt;http://www.keil.com/support/man/docs/uv4/uv4_b_filetypes.htm&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;
I seem to recall the promise that the new uVision project file
format would be &lt;i&gt;&amp;quot;Open&amp;quot;&lt;/i&gt; - but I see no evidence of that as
yet...&lt;/p&gt;

&lt;p&gt;
&lt;b&gt;:-(&lt;/b&gt;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/90110?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 10:26:39 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:3eed008d-6084-4ae6-968d-e94b577e0a11</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Trying to normalize the *.Opt file before the commit will allow a
diff to give at least some indication of what was changed.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/115377?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 10:13:43 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:08e78fbc-6169-45bd-8e56-664bf1a319c9</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;My solution is just to ensure that all windows are closed
before a check-in...&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Yes, this is the most annoying &amp;quot;feature&amp;quot;! sometimes I add files to
a project and forget to close uv3 before the check-in. result?
somebody else cannot build...!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/57226?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 10:13:18 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b7d23570-cb87-4355-8eea-0c89d1947d02</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;We only want to store the information that is absolutely
neccessary&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Why?&lt;/p&gt;

&lt;p&gt;
If you store a bit of extra information (eg, from the &lt;b&gt;.opt&lt;/b&gt;
file) that isn&amp;#39;t strictly necessary, what&amp;#39;s the problem?&lt;/p&gt;

&lt;p&gt;
On the other hand, if you omit something that later does turn out
to be important - then it&amp;#39;s too late!&lt;/p&gt;

&lt;p&gt;
Once it&amp;#39;s gone, it&amp;#39;s gone - so always better to store too much
than too little!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/103605?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 10:09:43 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:8fa3fb5b-aa39-422e-a11c-23f4c19a001e</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
The &lt;b&gt;.opt&lt;/b&gt; file is &lt;i&gt;supposed to be&lt;/i&gt; the one that
contains just the &amp;quot;user&amp;quot; settings - but this is broken.&lt;/p&gt;

&lt;p&gt;
&lt;b&gt;:-(&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;
IIRC, the 8051 tools stored the XTAL value in the &lt;b&gt;.opt&lt;/b&gt; file
- though it should be a &amp;quot;Project&amp;quot; setting in the &lt;b&gt;.uv2&lt;/b&gt;
file.&lt;/p&gt;

&lt;p&gt;
I&amp;#39;ve also found that keeping just the &lt;b&gt;.uv2&lt;/b&gt; file doesn&amp;#39;t
work entirely properly for ARM projects; eg, I &lt;i&gt;&lt;b&gt;think&lt;/b&gt;&lt;/i&gt;
(but haven&amp;#39;t bothered to confirm) that (some of) the debug settings
are in the &lt;b&gt;.opt&lt;/b&gt; file that should be in the &lt;b&gt;.uv2&lt;/b&gt; file -
which means that debugging doesn&amp;#39;t work properly after keeping only
the &lt;b&gt;.uv2&lt;/b&gt; file.&lt;/p&gt;

&lt;p&gt;
&lt;b&gt;:-(&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;
My solution is just to ensure that all windows are closed before a
check-in...&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/90113?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 08:14:50 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:de0ed234-5e95-46da-89ea-b50d8324126a</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Not sure if it is a good idea, but I store the *.Opt and *.Uv2
file in the repository.&lt;/p&gt;

&lt;p&gt;
When changing project options or adding/removing/rearranging
source files, I retrieve the current version from the repository.
Then I make the changes, saves the project and commit the changed
files.&lt;/p&gt;

&lt;p&gt;
The *.Opt file contains a huge amount of noise, so I don&amp;#39;t
normally commit any changes.&lt;/p&gt;

&lt;p&gt;
Keil should have considered a separate desktop file for
information about open source files or the current location/size of
the windows.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to put uVision project files under source control</title><link>https://community.arm.com/thread/57233?ContentTypeID=1</link><pubDate>Mon, 09 Nov 2009 08:01:34 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a5306682-10c3-45d5-93b7-b27b14d0f4f8</guid><dc:creator>Mike Kleshov</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;We only want to store the information that is absolutely
neccessary to rebuild the objects.&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
That would be source code files themselves and build instructions.
The uVision project file stores more information than this.&lt;br /&gt;
Perhaps you should not place uVision files under version control.
Instead, write a Makefile. The only thing is, if you want to run a
debugger you must have a project file.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>