AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Correct instructions for building wx applications with MSVC.

Browse Source 
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
This commit is contained in:
Vadim Zeitlin 2014-08-10 16:11:54 +00:00
parent 3a0c01cbea
commit ffcfcb526f
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/msw/install.txt
View File

@ -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.