Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use PlatformToolsetVersion in MSVC binaries usage instructions

Browse Source 
This should work for any compiler version, at the cost of being slightly
less clear.

Closes #18422.
This commit is contained in:
Vadim Zeitlin
2019-06-25 16:58:56 +02:00
parent fb2f5916b2
commit 8afa383097
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/msw/binaries.md
View File

@@ -71,12 +71,14 @@ following:
* Check that you use "Multi-threaded \[Debug\] DLL" in the "Run-time * Check that you use "Multi-threaded \[Debug\] DLL" in the "Run-time
library" option under "Code Generation" to ensure that your build uses library" option under "Code Generation" to ensure that your build uses
the same CRT version as our binaries. the same CRT version as our binaries.
* In the linker options you only need to add `$``(wxwin)\lib\vc141_dll` (with * In the linker options you only need to add `$``(wxwin)\lib\vc$``(PlatformToolsetVersion)_dll`
the compiler-version-dependent suffix, of course) to "Additional Library (the standard `PlatformToolsetVersion` macro expands into something like
Directories" under "Linker\\General" in the options. Thanks to the use of `141`, depending on the toolset version being used, and you could also use
MSVC-specific `setup.h` you don't need to list wxWidgets libraries manually, the version number directly if you prefer) to "Additional Library
i.e. you do **not** need to put anything in the list of "Additional Directories" under "Linker\\General" in the options. Thanks to the use of
Dependencies". MSVC-specific `setup.h` you don't need to list wxWidgets libraries manually,
i.e. you do **not** need to put anything in the list of "Additional
Dependencies".
Now you should be able to build your project successfully, both in "Debug" and Now you should be able to build your project successfully, both in "Debug" and
"Release" configurations. With MSVS 10 or newer it can also be done from the "Release" configurations. With MSVS 10 or newer it can also be done from the