summaryrefslogtreecommitdiffstatshomepage
path: root/3rdparty/expat/win32/README.txt
diff options
context:
space:
mode:
Diffstat (limited to '3rdparty/expat/win32/README.txt')
-rw-r--r--3rdparty/expat/win32/README.txt52
1 files changed, 16 insertions, 36 deletions
diff --git a/3rdparty/expat/win32/README.txt b/3rdparty/expat/win32/README.txt
index e3702ae6217..d1069cdd2f0 100644
--- a/3rdparty/expat/win32/README.txt
+++ b/3rdparty/expat/win32/README.txt
@@ -1,26 +1,22 @@
-Expat can be built on Windows in three ways:
- using MS Visual C++ (6.0 or .NET), Borland C++ Builder 5 or Cygwin.
+Expat can be built on Windows in two ways:
+ using MS Visual Studio .NET or Cygwin.
* Cygwin:
This follows the Unix build procedures.
-* C++ Builder 5:
- Possible with make files in the BCB5 subdirectory.
- Details can be found in the ReadMe file located there.
+* MS Visual Studio 2008, 2010, 2013, 2015 and 2017:
+ Use CMake to generate a solution file for Visual Studio, then use msbuild
+ to compile. For example:
-* MS Visual C++ 6:
- Based on the workspace file expat.dsw. The related project
- files (.dsp) are located in the lib subdirectory.
-
-* MS Visual Studio .NET 2002, 2003, 2005, 2008, 2010:
- The VC++ 6 workspace file (expat.dsw) and project files (.dsp)
- can be opened and imported in VS.NET without problems.
+ 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:
@@ -42,39 +38,23 @@ Expat can be built on Windows in three ways:
Dynamic Linking:
- By default the Expat Dlls are built to link statically
+ By default the Expat Dlls are built to link dynamically
with the multi-threaded run-time library.
The libraries are named
- libexpat(w).dll
- libexpat(w).lib (import library)
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.
+ Versions that are statically linking with the multi-threaded run-time library
+ can be built with -DEXPAT_MSVC_STATIC_CRT=ON.
- Static Linking:
+ Static Linking: (through -DEXPAT_SHARED_LIBS=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.