aboutsummaryrefslogtreecommitdiff
path: root/windows
diff options
context:
space:
mode:
authorLasse Collin <lasse.collin@tukaani.org>2023-01-10 00:33:14 +0200
committerLasse Collin <lasse.collin@tukaani.org>2023-01-10 00:35:09 +0200
commit6e652ceb18c615c578c869db300fa0756788b4e0 (patch)
tree5b1ac8d31790f2695d852a103e8ff6e0caccb8c0 /windows
parentCMake: Fix windres issues again. (diff)
downloadxz-6e652ceb18c615c578c869db300fa0756788b4e0.tar.xz
Windows: Update INSTALL-MSVC.txt to recommend CMake over project files.
Diffstat (limited to 'windows')
-rw-r--r--windows/INSTALL-MSVC.txt19
1 files changed, 12 insertions, 7 deletions
diff --git a/windows/INSTALL-MSVC.txt b/windows/INSTALL-MSVC.txt
index 17e1da18..2fdd1e7b 100644
--- a/windows/INSTALL-MSVC.txt
+++ b/windows/INSTALL-MSVC.txt
@@ -18,7 +18,11 @@ Introduction
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.
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
you may need to set the target platform version before building.
- Currently no test programs are built or run under MSVC.
-
- 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.
+ Currently no test programs are built or run under MSVC from the
+ project files. CMake-based builds include tests too.
Notes
@@ -49,3 +49,8 @@ Notes
by default. To avoid this when using static liblzma from your code,
#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.
+