revi-archive/xz-archive
1
0
Fork 0
mirror of https://git.tukaani.org/xz.git synced 2024-04-04 12:36:23 +02:00
Code Activity

Windows: Update INSTALL-MSVC.txt to recommend CMake over project files.

Browse source
This commit is contained in:
Lasse Collin 2023-01-10 00:33:14 +02:00
parent 6b117d3b1f
commit 6e652ceb18
1 changed files with 12 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
windows/INSTALL-MSVC.txt
View file

@ -18,7 +18,11 @@ Introduction
Building Building
-------- --------
The following files in this directory are for MSVC: It is recommended to use CMake to generate build files for MSVC.
The project files in vs201x directories will be removed in the
future (5.4.x releases will include them still).
Descriptions of the files in the vs201x directories:
config.h liblzma configuration #defines for MSVC. config.h liblzma configuration #defines for MSVC.
liblzma.vcxproj This builds static liblzma. liblzma.vcxproj This builds static liblzma.
@ -34,12 +38,8 @@ Building
This means that you may need to either install Windows SDK 8.1 or This means that you may need to either install Windows SDK 8.1 or
you may need to set the target platform version before building. you may need to set the target platform version before building.
Currently no test programs are built or run under MSVC. Currently no test programs are built or run under MSVC from the
project files. CMake-based builds include tests too.
MSVC gives a bunch of compiler warnings. Some warnings are specific
to 32-bit or 64-bit build and some appear for both builds. These
are known and shouldn't be a problem. Some of them will probably
be fixed in the future.
Notes Notes
@ -49,3 +49,8 @@ Notes
by default. To avoid this when using static liblzma from your code, by default. To avoid this when using static liblzma from your code,
#define LZMA_API_STATIC before #including <lzma.h>. #define LZMA_API_STATIC before #including <lzma.h>.
MSVC gives a bunch of compiler warnings. Some warnings are specific
to 32-bit or 64-bit build and some appear for both builds. These
are known and shouldn't be a problem. Some of them will probably
be fixed in the future.