Wireshark mailing list archives
Is there any reason to give our libraries "libXXX.{dll, lib}" names on Windows?
From: Guy Harris <guy () alum mit edu>
Date: Wed, 9 Jul 2014 18:06:49 -0700
On UN*X, the file names for libraries begin with "lib" - the linkers all look for "libfoo.*" if you link with "-lfoo". On Windows, that's not the case. Is there any reason for us to put "lib" at the beginning of the file names for the wsutil, wiretap, wireshark, etc. libraries? I infer from https://code.wireshark.org/review/2957 that CMake might, by default, not put "lib" there, requiring us to, in the CMake build, force it to be there on Windows by adding some stuff to the CMakeLists.txt files. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Is there any reason to give our libraries "libXXX.{dll, lib}" names on Windows? Guy Harris (Jul 09)
- Re: Is there any reason to give our libraries "libXXX.{dll, lib}" names on Windows? Graham Bloice (Jul 09)
- Re: Is there any reason to give our libraries "libXXX.{dll, lib}" names on Windows? Graham Bloice (Jul 09)
- Re: Is there any reason to give our libraries "libXXX.{dll, lib}" names on Windows? Guy Harris (Jul 10)
- Re: Is there any reason to give our libraries "libXXX.{dll, lib}" names on Windows? Graham Bloice (Jul 09)