From ffcfcb526f23779d395cdf7a559d906ce43a0da7 Mon Sep 17 00:00:00 2001 From: Vadim Zeitlin Date: Sun, 10 Aug 2014 16:11:54 +0000 Subject: [PATCH] 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/trunk@77051 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/msw/install.txt | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/docs/msw/install.txt b/docs/msw/install.txt index e9432a8944..d2b0e411f4 100644 --- a/docs/msw/install.txt +++ b/docs/msw/install.txt @@ -473,7 +473,9 @@ NB: The makefiles and project files provided with wxWidgets samples show which sample and adapt it to your application. 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 - compiler @@ -497,7 +499,8 @@ following to use wxWidgets: (all wxWidgets applications use the base library). -Microsoft Visual C++ users can simplify the linker setup by prepending the -directory $WXWIN/msvc to the include path (it must come before $WXWIN/include -directory!) and omitting the last step: the required libraries will be linked -in automatically using the "#pragma comment(lib)" feature of this compiler. +Microsoft Visual C++ users can simplify the linker setup by prepending +"$(WXWIN)/include/msvc" to the include path (it must come before the +"$(WXWIN)/include" part!) and omitting the last step: the required libraries +will be linked in automatically using the "#pragma comment(lib)" feature of +this compiler.