summaryrefslogtreecommitdiff
path: root/expat/win32
diff options
context:
space:
mode:
authorSebastian Pipping <sebastian@pipping.org>2019-08-29 01:36:55 +0200
committerSebastian Pipping <sebastian@pipping.org>2019-08-29 02:34:14 +0200
commit7ae689fd95bf13c85fe632740cb04355a1c0c8d8 (patch)
treed3bbaaf754b4d36f538765bba58e90cf3f9e5807 /expat/win32
parentf42417b92c4b4440e50968a329acee8bda73dc30 (diff)
downloadlibexpat-git-7ae689fd95bf13c85fe632740cb04355a1c0c8d8.tar.gz
docs: Migrate to generated solution files with CMake and msbuild on Windows
Diffstat (limited to 'expat/win32')
-rw-r--r--expat/win32/README.txt39
1 files changed, 12 insertions, 27 deletions
diff --git a/expat/win32/README.txt b/expat/win32/README.txt
index 462c49b7..3d1f79ca 100644
--- a/expat/win32/README.txt
+++ b/expat/win32/README.txt
@@ -6,16 +6,17 @@ Expat can be built on Windows in two ways:
This follows the Unix build procedures.
* MS Visual Studio 2013, 2015 and 2017:
- A solution file for Visual Studio 2013 is provided: expat.sln.
- The associated project files (*.vcxproj) reside in the appropriate
- project directories. This solution file can be opened in VS 2015 or VS 2017
- and should be upgraded automatically if VS 2013 is not also installed.
- Note: Tests have their own solution files.
+ Use CMake to generate a solution file for Visual Studio, then use msbuild
+ to compile. For example:
+
+ md build
+ cd build
+ cmake -G"Visual Studio 15 2017" -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
+ msbuild /m expat.sln
* All MS C/C++ compilers:
- The output for all projects will be generated in the win32\bin
- directory, intermediate files will be located in project-specific
- subdirectories of win32\tmp.
+ The output for all projects will be generated in the <CMAKE_BUILD_TYPE>\
+ and xmlwf\<CMAKE_BUILD_TYPE>\ directories.
* Creating MinGW dynamic libraries from MS VC++ DLLs:
@@ -45,31 +46,15 @@ Expat can be built on Windows in two ways:
The "w" indicates the UTF-16 version of the library.
One rarely uses other versions of the Dll, but they can
- be built easily by specifying a different RTL linkage in
- the IDE on the C/C++ tab under the category Code Generation.
+ be built with -DMSVC_USE_STATIC_CRT=OFF.
- Static Linking:
+ Static Linking: (through -DBUILD_shared=OFF)
The libraries should be named like this:
- Single-theaded: libexpat(w)ML.lib
Multi-threaded: libexpat(w)MT.lib
Multi-threaded Dll: libexpat(w)MD.lib
The suffixes conform to the compiler switch settings
- /ML, /MT and /MD for MS VC++.
-
- Note: In Visual Studio 2005 (Visual C++ 8.0) and later, the
- single-threaded runtime library is not supported anymore.
-
- By default, the expat-static and expatw-static projects are set up
- to link statically against the multithreaded run-time library,
- so they will build libexpatMT.lib or libexpatwMT.lib files.
-
- To build the other versions of the static library,
- go to Project - Settings:
- - specify a different RTL linkage on the C/C++ tab
- under the category Code Generation.
- - then, on the Library tab, change the output file name
- accordingly, as described above
+ /MT and /MD for MS VC++.
An application linking to the static libraries must
have the global macro XML_STATIC defined.