Wireshark mailing list archives
Visual Studio 2013/2015/2017 compatibility and libraries
From: Peter Wu <peter () lekensteyn nl>
Date: Mon, 24 Apr 2017 15:43:36 +0200
Hi, Are there possible issues to be aware of when using the libraries (built with mingw/msvc2013) with the Wireshark binaries built with VS2017? When trying it with a friend, it seems to build and run with no issues. I thought that there can be problems with combining different MSVC runtime versions in one binary? Looking through the libraries, it seems that there is a combination of at least MingW (GeoIP?) and MSVC (Lua). (And apparently VS2015 (14.0) and VS2017 (14.1) are binary compatible.) Note: I am developing for Linux and know little about the MS ecosystem, but for testing under Windows, VS2015 or newer is attractive because you can install a subset of the tools without pulling the full bloat of VS (using Visual C++ Build Tools). -- Kind regards, Peter Wu https://lekensteyn.nl ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Visual Studio 2013/2015/2017 compatibility and libraries Peter Wu (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Pascal Quantin (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Peter Wu (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Pascal Quantin (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Graham Bloice (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Pascal Quantin (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Graham Bloice (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Peter Wu (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Graham Bloice (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Peter Wu (Apr 24)
- Re: Visual Studio 2013/2015/2017 compatibility and libraries Pascal Quantin (Apr 24)