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

Fix formatting of wxMSW build instructions

Browse Source 
Using numbered lists with multiline items doesn't work in Markdown, so
remove it.

Also put the "IDE" part of the instructions before the "command line"
one, as it is probably use much more commonly.

No real changes to contents.
This commit is contained in:
Vadim Zeitlin 2021-07-13 14:30:54 +02:00
parent 9028ae74fc
commit 74c51eaff2
1 changed files with 38 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
docs/msw/install.md
View File

@ -47,18 +47,34 @@ All makefiles and project are located in build\msw directory.
Microsoft Visual C++ Compilation {#msw_build_msvs} Microsoft Visual C++ Compilation {#msw_build_msvs}
---------------------------------------------------------------- ----------------------------------------------------------------
* From command line using the provided makefiles: ### From the IDE
0. Open a "Visual Studio Command Prompt" window shortcut to which Ready to use project files are provided for VC++ versions 8, 9,
must have been installed to the "Start" menu or the "Start" screen 10, 11, 12, 14, 15 and 16 (also known as MSVS 2005, 2008, 2010, 2012,
2013, 2015, 2017 and 2019 respectively).
Simply open `wx_vcN.sln` (for N=8, 9, 10, 11, 12, 14, 15 or 16) file,
select the appropriate configuration (Debug or Release, static or DLL)
and build the solution. Notice that when building a DLL configuration,
you may need to perform the build several times because the projects
are not always built in the correct order, and this may result in link
errors. Simply do the build again, up to 3 times, to fix this.
### From the command line
wxWidgets can also be built from the command line using the provided makefiles.
This needs to be done from the "Visual Studio Command Prompt" window, which can
be opened using a shortcut installed to the "Start" menu or the "Start" screen
by MSVS installation. by MSVS installation.
1. Change directory to \%WXWIN\%\build\msw and type In this window, change directory to `%WXWIN\%\build\msw` and type
> nmake /f makefile.vc > nmake /f makefile.vc
to build wxWidgets in the default debug configuration as a static to build wxWidgets in the default debug configuration as a static library. You
library. You can also do can also do
> nmake /f makefile.vc BUILD=release > nmake /f makefile.vc BUILD=release
@ -72,28 +88,14 @@ Microsoft Visual C++ Compilation {#msw_build_msvs}
to build a 64 bit release DLL version from an x64 command prompt. to build a 64 bit release DLL version from an x64 command prompt.
See "Configuring the Build" for more information about the See "Configuring the Build" for more information about the additional
additional parameters that can be specified on the command line. parameters that can be specified on the command line.
2. To verify your build, change the directory to \%WXWIN\%\samples\minimal and To verify your build, change the directory to `%WXWIN\%\samples\minimal` and
run the same nmake command (with the same parameters there), this run the same nmake command (with the same parameters there), this should create
should create a working minimal wxWidgets sample. a working minimal wxWidgets sample.
3. If you need to rebuild, use "clean" target first or "nmake /a". If you need to rebuild, use "clean" target first or "nmake /a".
* From the IDE using the provided project files:
Ready to use project files are provided for VC++ versions 8, 9,
10, 11, 12, 14, 15 and 16 (also known as MSVS 2005, 2008, 2010, 2012,
2013, 2015, 2017 and 2019 respectively).
Simply open `wx_vcN.sln` (for N=8, 9, 10, 11, 12, 14, 15 or 16) file,
select the appropriate configuration (Debug or Release, static or DLL)
and build the solution. Notice that when building a DLL configuration,
you may need to perform the build several times because the projects
are not always built in the correct order, and this may result in link
errors. Simply do the build again, up to 3 times, to fix this.
### Special notes for Visual Studio 2010+ ### Special notes for Visual Studio 2010+