• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 947 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with LIB51 and upper/lower case names

Andrew E. Kalman

I'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 bash shell running "under" Win98 or Win2000, I end up with SILLY.LIB.

What I really want is an all-lower-case silly.lib.

4 other compilers I use (gcc, HI-TECH PICC, HI-TECH V8C, CodeWarrior) preserve filename case in this situation.

Is there a way to preserve the filename's case when building a library with LIB51.EXE?

Thanks,

  • 0

    This is an operating system issue, not a LIB51 issue!

    In the beginning, MS-DOS stored all filemames on the disk in UPPERCASE, but all commands were case-insensitive; ie, dir a* and DIR A* would give exactly the same results.

    Win3.x FileManager introduced the idea of displaying the filenames in lowercase (even though they were uppercase on the disk)

    Win9x preserves the case on the disk, but added this funny idea of (nearly?) always displaying the initial letter Uppercase.

    If you use the Win9x/NT command-line dir, with the full display of both short & long filenames, you will see that the short filenames are always all UPPERCASE, and the long names preserve case.
    So the differences you are seeing with different products probably just depend on which particular API the implementors have used.

    As the PC is not case sensitive anyway, why are you worried?

  • 0 in reply to Andrew Neil

    Hi Andrew.

    I agree that it's mainly an OS issue, but the makefile that'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's output results in upper-case letters in the filename.

    So I think there's something more than just the OS at issue here ...

    Anyway, I found a PERL script that forces lowercase on a directory's files rather nicely.

    As to why ... ALL-UPPERCASE LETTERS ARE VERY HARD ON THE EYES ... :-)

    Regards,