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

Quote paths using backslashes in Doxygen input

Browse Source 
Otherwise Doxygen interprets each path component as its command and
complains about "unknown \msw command" in "build\msw" path, for example.
This commit is contained in:
Vadim Zeitlin
2022-03-28 00:16:29 +02:00
parent 9dc7248b1d
commit a406e2a7dc
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/msw/gtk.md
View File

@@ -25,7 +25,7 @@ Regenerate required make/project files:
3. Download GTK+ for Windows and uncompress files in the directory
without spaces in the name. We suppose later that GTK+/Win32 is
in the C:\gtk directory.
in the `C:\gtk` directory.
http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.24/gtk+_2.24.10-1_win32.zip
@@ -48,11 +48,11 @@ and library directory
See http://msdn.microsoft.com/en-us/library/t9az1d21(v=vs.90).aspx
Open solution file in build\msw directory, select "GTK+ Debug" solution
Open solution file in `build\msw` directory, select "GTK+ Debug" solution
configuration and build the solution. To be sure that everything is as expected
you can build minimal sample.
GTK+ is linked to wxWidgets always as DLL, so C:\gtk\bin directory should be
GTK+ is linked to wxWidgets always as DLL, so `C:\gtk\bin` directory should be
in %PATH% environment variable before application run.
4.2 You can also build using nmake:

6
docs/msw/install.md
View File

@@ -42,7 +42,7 @@ The following sections explain how to compile wxWidgets with each supported
compiler, see the "Building Applications" section about the instructions for
building your application using wxWidgets.
All makefiles and project are located in build\msw directory.
All makefiles and project are located in `build\msw` directory.
Microsoft Visual C++ Compilation {#msw_build_msvs}
----------------------------------------------------------------
@@ -119,7 +119,7 @@ contributors. If the version is out of date, please [create an issue or pull req
### Special notes for Visual Studio 2010+
For Visual Studio 2010+ solutions it is possible to customize the build by
creating a `wx_local.props` file in the build\msw directory which is used, if it
creating a `wx_local.props` file in the `build\msw` directory which is used, if it
exists, by the projects. The settings in that file override the default values
for the properties such as wxCfg (corresponding to the CFG makefile variable
described below) or wxVendor (corresponding to VENDOR). The typical way to
@@ -239,7 +239,7 @@ executed from a DOS command line window (cmd.exe, *not* Bash sh.exe).
make command without `setup_h` at the end to work around a bug
in the current makefiles.
2. To verify your build, change the directory to samples\minimal and
2. To verify your build, change the directory to `samples\minimal` and
run the same mingw32-make command (with the same parameters there),
this should create a working minimal wxWidgets sample.