<?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 LIB51 and upper/lower case names</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/14573/problem-with-lib51-and-upper-lower-case-names</link><description> I&amp;#39;m having a problem with the filenames that LIB51 generates. 
 
Under Win98, if I do: 
 
 lib51.exe TRANSFER a.obj, b.obj TO silly.lib 
 
I end up with a library called Silly.lib when viewed from Windows explorer. 
 
If I do the same from within a Cygwin</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Problem with LIB51 and upper/lower case names</title><link>https://community.arm.com/thread/53960?ContentTypeID=1</link><pubDate>Sat, 10 Nov 2001 19:00:22 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:9d8bbad8-6cdb-48dc-912f-e0ea80d4e3e6</guid><dc:creator>Andrew E. Kalman</dc:creator><description>&lt;p&gt;Hi Andrew.&lt;br /&gt;
&lt;br /&gt;
I agree that it&amp;#39;s &lt;b&gt;mainly&lt;/b&gt; an OS issue, but the makefile that&amp;#39;s driving the libarians of all the other 4 listed compilers is feeding filenames to them the same way as it feeds LIB51 -- yet only LIB51&amp;#39;s output results in upper-case letters in the filename.&lt;br /&gt;
&lt;br /&gt;
So I think there&amp;#39;s something more than just the OS at issue here ...&lt;br /&gt;
&lt;br /&gt;
Anyway, I found a PERL script that forces lowercase on a directory&amp;#39;s files rather nicely.&lt;br /&gt;
&lt;br /&gt;
As to why ... ALL-UPPERCASE LETTERS ARE VERY HARD ON THE EYES ... :-)&lt;br /&gt;
&lt;br /&gt;
Regards,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem with LIB51 and upper/lower case names</title><link>https://community.arm.com/thread/38030?ContentTypeID=1</link><pubDate>Sat, 10 Nov 2001 13:54:59 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:318f503f-f74f-4dc4-9e2e-11f44ec1ea73</guid><dc:creator>Andrew Neil</dc:creator><description>&lt;p&gt;This is an operating system issue, not a LIB51 issue!&lt;br /&gt;
&lt;br /&gt;
In the beginning, MS-DOS stored all filemames on the disk in UPPERCASE, but all commands were case-insensitive; &lt;i&gt;ie,&lt;/i&gt; &lt;b&gt;dir a*&lt;/b&gt; and &lt;b&gt;DIR A*&lt;/b&gt; would give exactly the same results.&lt;br /&gt;
&lt;br /&gt;
Win3.x FileManager introduced the idea of displaying the filenames in lowercase (even though they were uppercase on the disk)&lt;br /&gt;
&lt;br /&gt;
Win9x preserves the case on the disk, but added this funny idea of (nearly?) always displaying the initial letter Uppercase.&lt;br /&gt;
&lt;br /&gt;
If you use the Win9x/NT command-line dir, with the full display of both short &amp;amp; long filenames, you will see that the short filenames are always all UPPERCASE, and the long names preserve case.&lt;br /&gt;
So the differences you are seeing with different products probably just depend on which particular API the implementors have used.&lt;br /&gt;
&lt;br /&gt;
As the PC is not case sensitive anyway, why are you worried?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>