<?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>Make Files and uVision2</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/14090/make-files-and-uvision2</link><description> I&amp;#39;m using uVision2 v2.12. Does it produce make files for others to use? What if you want someone to be able to build files without having to know anything about uVision? I don&amp;#39;t want to use uVision2 and then have to turn around and hand produce make</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Make Files and uVision2</title><link>https://community.arm.com/thread/94767?ContentTypeID=1</link><pubDate>Thu, 03 May 2001 09:41:35 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:86abd299-885a-49da-8b81-2f26c518383e</guid><dc:creator>Jon Ward</dc:creator><description>&lt;p&gt;Thanks, Andrew.  :-)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Make Files and uVision2</title><link>https://community.arm.com/thread/53641?ContentTypeID=1</link><pubDate>Thu, 03 May 2001 05:57:38 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:ab373c25-508a-4327-bc93-a33d5126f149</guid><dc:creator>Andrew Neil</dc:creator><description>&lt;p&gt;&lt;a href="http://www.keil.com/support/docs/868.htm"&gt;http://www.keil.com/support/docs/868.htm&lt;/a&gt;&lt;br /&gt;
Refers to the C166 document, but the principle&amp;#39;s exactly the same for C51.&lt;br /&gt;
The document is GS51.pdf - you can open it from the &amp;#39;Books&amp;#39; tab in the uVision Project window.&lt;br /&gt;
&lt;br /&gt;
All the C51 tools can be run individually from the command-line, so there&amp;#39;s nothing to stop you creating a makefile if you want to.&lt;br /&gt;
uVision shows you the command line options at the foot of each tab in the &amp;quot;Target Options.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you write your code carefully, you can make it compile under other tools (MSVC, Borland, etc) - then you could use those tools to create the dependencies etc for your makefile and adapt it for the Keil tools as appropriate.&lt;br /&gt;
&lt;br /&gt;
Doing so can also give you other benefits - like better diagnostics, browsing, etc&lt;br /&gt;
NB: You only want it to &lt;b&gt;compile&lt;/b&gt; - making it &lt;b&gt;run&lt;/b&gt; on another target is a whole new ballgame...!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Make Files and uVision2</title><link>https://community.arm.com/thread/37467?ContentTypeID=1</link><pubDate>Wed, 02 May 2001 17:15:55 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b87e83eb-ef72-4921-a1d2-c54bfe367402</guid><dc:creator>Keil Support</dc:creator><description>&lt;p&gt;You can run uVision2 from the command line to build a project.  Ergo, you can create a batch file that simply provides the correct command line to uVision2.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.keil.com/support/docs/868.htm"&gt;http://www.keil.com/support/docs/868.htm&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Jon&lt;/b&gt;&lt;br /&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>