From: Paul G. <pgarceau@at...> - 2002-09-09 01:29:34
After reading this, my immediate, and very strong gut reaction was "no".
> The Win32 port of binutils supports foo.lib style naming convention. It
> will even find foo.dll as a last resort if the path to foo.dll is in the
> library search paths. So, with this in mind, the naming convention that
> I would like to see is, if the library created by mingw32-gcc can be
> used by MSVC then name the file foo.lib, otherwise name it libfoo.a.
> This now brings us to an issue for mingw-runtime and w32api, should we
> change the name of the libraries to match a new standard?
Imho, not generically. As maintainers, it might proove to be far more work then it is
worth as not everybody who uses gcc (as their main compiler) even cares to _generate_ .lib
files. Being able to _read_ .lib files might be a different question.
Changing the name of all the libraries to match a new standard, imho, might not be
a good idea. Making it possible for people to choose which type static library they want to
_generate_, however, might be worth considering.
Get latest updates about Open Source Projects, Conferences and News.