Wireshark mailing list archives
Re: Is there any reason to give our libraries "libXXX.{dll, lib}" names on Windows?
From: Guy Harris <guy () alum mit edu>
Date: Thu, 10 Jul 2014 01:27:04 -0700
On Jul 9, 2014, at 11:30 PM, Graham Bloice <graham.bloice () trihedral com> wrote:
One other piece of info, without this change, CMake produces a wireshark.exe and a wireshark.dll and the .pdb file for the dll gets overwritten by the one for the exe.
And the nmake build would probably do the same thing. Might as well leave the "lib" in there, then, so the debugger stuff doesn't have any name collisions. ___________________________________________________________________________ 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)