<?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>Problem with user commands</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/28021/problem-with-user-commands</link><description> 
Hi all, 

 
I want to use a user command to post-process the axf file. I
enclose the command in quotes to preserve spaces in the path.
However, if I also use quotes to enclose parameters in quotes, then
the external command does not get called. If I</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Problem with user commands</title><link>https://community.arm.com/thread/59667?ContentTypeID=1</link><pubDate>Thu, 21 Jul 2011 13:38:40 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:ad3127ba-23ee-43fb-912a-8bae8c142e6d</guid><dc:creator>HansBernhard Broeker</dc:creator><description>&lt;p&gt;&lt;p&gt;
The essence of the reply is: &lt;b&gt;Don&amp;#39;t do that, then&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;
The &amp;quot;that&amp;quot; in question here is &amp;quot;store stuff in paths that contain
blanks&amp;quot;.&lt;br /&gt;
Nor any other funny characters, for that matter.&lt;br /&gt;
It just doesn&amp;#39;t work in the long run.&lt;/p&gt;

&lt;p&gt;
It took Microsoft in their infinite &amp;quot;wisdom&amp;quot; only about one decade
to finally revert their position of trying to ram down everybody&amp;#39;s
throat the entirely,&lt;br /&gt;
obviously gratuitous choice for &amp;quot;c:\Documents and Settings&amp;quot;.&lt;br /&gt;
The only aspect of that choice that ever made the least bit of sense
(as perverted as it is) was that it&lt;br /&gt;
&lt;b&gt;forced&lt;/b&gt; every Windows programmer to try and support blanks in
paths. Most eventually succeeded to some more or less sufficient
extent.&lt;/p&gt;

&lt;p&gt;
Only then, after had finally gotten on everybody&amp;#39;s nerves enough,
did Microsoft finally switch back to what would obviously have been
the&lt;br /&gt;
right choice all along: &amp;quot;c:\Users&amp;quot;. Mission accomplished,
apparently.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem with user commands</title><link>https://community.arm.com/thread/118194?ContentTypeID=1</link><pubDate>Thu, 21 Jul 2011 09:19:25 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a67e1387-a659-4937-b0d9-8781210f0375</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;is there any solution for this problem?&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Not really, I&amp;#39;m afraid.&lt;/p&gt;

&lt;p&gt;
The only really safe way is to just avoid all spaces in pathnames
for this kind of thing.&lt;/p&gt;

&lt;p&gt;
Even if you manage to come up with a &amp;quot;fix&amp;quot; for this particular
situation, you&amp;#39;ll just get bitten again by the same problem somewhere
else later on...&lt;/p&gt;

&lt;p&gt;
Spaces and comman-line tools basically just don&amp;#39;t mix - and prety
much all development tools rely upon the command line at some
point.&lt;/p&gt;

&lt;p&gt;
BTW:&lt;/p&gt;

&lt;p&gt;
I had the same problem years ago with uVision-&lt;b&gt;2&lt;/b&gt;.&lt;br /&gt;
I did think at the time that Keil&amp;#39;s handling was broken.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>