aboutsummaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorLasse Collin <lasse.collin@tukaani.org>2022-12-13 20:29:39 +0200
committerLasse Collin <lasse.collin@tukaani.org>2022-12-13 20:29:39 +0200
commit20869eb3fb280ff4f271ef527b12b6bf68b05e19 (patch)
treefe62ac40c75416e42cea410f92e6ac142d13d951 /INSTALL
parentAdd NEWS for 5.4.0. (diff)
downloadxz-20869eb3fb280ff4f271ef527b12b6bf68b05e19.tar.xz
Update INSTALL: CMake on Windows isn't experimental anymore.
Using CMake to build liblzma should work on a few other OSes but building the command line tools is still subtly broken. It is known that shared library versioning may differ between CMake and Libtool builds on some OSes, most notably Darwin.
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL10
1 files changed, 4 insertions, 6 deletions
diff --git a/INSTALL b/INSTALL
index bf1e9c31..67df1880 100644
--- a/INSTALL
+++ b/INSTALL
@@ -142,12 +142,10 @@ XZ Utils Installation
If it is enough to build liblzma (no command line tools):
- - There is experimental CMake support. As it is, it should be
- good enough to build static liblzma with Visual Studio.
- Building liblzma.dll might work too (if it doesn't, it should
- be fixed). The CMake support may work with MinGW or MinGW-w64.
- Read the comment in the beginning of CMakeLists.txt before
- running CMake!
+ - There is CMake support. It should be good enough to build
+ static liblzma or liblzma.dll with Visual Studio. The CMake
+ support may work with MinGW or MinGW-w64. Read the comment
+ in the beginning of CMakeLists.txt before running CMake!
- There are Visual Studio project files under the "windows"
directory. See windows/INSTALL-MSVC.txt. In the future the