Correct instructions for building wx applications with MSVC.

Use the correct $WXWIN/include/msvc path instead of the non-existing
$WXWIN/msvc.

Also mention that $WXWIN should actually be $(WXWIN) for MSVC.

Closes #16410.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_3_0_BRANCH@77049 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2014-08-10 16:11:34 +00:00
parent 6f64d8e394
commit 8012c1b8b3

View File

@@ -465,7 +465,9 @@ NB: The makefiles and project files provided with wxWidgets samples show which
sample and adapt it to your application. sample and adapt it to your application.
Independently of the compiler and make/IDE you are using you must do the Independently of the compiler and make/IDE you are using you must do the
following to use wxWidgets: following to use wxWidgets sources under the directory $WXWIN (notice that
different tool chains refer to environment variables such as WXWIN in
different ways, e.g. MSVC users should use $(WXWIN) instead of just $WXWIN):
* Add $WXWIN/include to the * Add $WXWIN/include to the
- compiler - compiler
@@ -489,7 +491,8 @@ following to use wxWidgets:
(all wxWidgets applications use the base library). (all wxWidgets applications use the base library).
Microsoft Visual C++ users can simplify the linker setup by prepending the Microsoft Visual C++ users can simplify the linker setup by prepending
directory $WXWIN/msvc to the include path (it must come before $WXWIN/include "$(WXWIN)/include/msvc" to the include path (it must come before the
directory!) and omitting the last step: the required libraries will be linked "$(WXWIN)/include" part!) and omitting the last step: the required libraries
in automatically using the "#pragma comment(lib)" feature of this compiler. will be linked in automatically using the "#pragma comment(lib)" feature of
this compiler.