From a424f7f173a85774f841ddf974b507c60521e127 Mon Sep 17 00:00:00 2001 From: "John W. Parent" <45471568+johnwparent@users.noreply.github.com> Date: Fri, 20 Jan 2023 16:32:28 -0500 Subject: Identify Windows support with tags (#35027) All packages with explicit Windows support can be found with `spack list --tags=windows`. This also removes the documentation which explicitly lists supported packages on Windows (which is currently out of date and is now unnecessary with the added tags). Note that if a package does not appear in this list, it *may* still build on Windows, but it likely means that no explicit attempt has been made to support it. --- lib/spack/docs/getting_started.rst | 29 ++++++++--------------------- 1 file changed, 8 insertions(+), 21 deletions(-) (limited to 'lib') diff --git a/lib/spack/docs/getting_started.rst b/lib/spack/docs/getting_started.rst index 3c11632fe4..253b0e41e5 100644 --- a/lib/spack/docs/getting_started.rst +++ b/lib/spack/docs/getting_started.rst @@ -1700,29 +1700,15 @@ If in the previous step, you did not have CMake or Ninja installed, running the Windows Compatible Packages """"""""""""""""""""""""""" -Many Spack packages are not currently compatible with Windows, due to Unix -dependencies or incompatible build tools like autoconf. Here are several -packages known to work on Windows: - -* abseil-cpp -* bzip2 -* clingo -* cpuinfo -* cmake -* hdf5 -* glm -* nasm -* netlib-lapack (requires Intel Fortran) -* ninja -* openssl -* perl -* python -* ruby -* wrf -* zlib +Not all spack packages currently have Windows support. Some are inherently incompatible with the +platform, and others simply have yet to be ported. To view the current set of packages with Windows +support, the list command should be used via `spack list -t windows`. If there's a package you'd like +to install on Windows but is not in that list, feel free to reach out to request the port or contribute +the port yourself. .. note:: - This is by no means a comprehensive list + This is by no means a comprehensive list, some packages may have ports that were not tagged + while others may just work out of the box on Windows and have not been tagged as such. ^^^^^^^^^^^^^^ For developers @@ -1734,3 +1720,4 @@ Instructions for creating the installer are at https://github.com/spack/spack/blob/develop/lib/spack/spack/cmd/installer/README.md Alternatively a pre-built copy of the Windows installer is available as an artifact of Spack's Windows CI +available at each run of the CI on develop or any PR. -- cgit v1.2.3-70-g09d2