-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Externally Controlled CMake Binaries #227
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
for package managers like Spack (spack/spack#28760), we are able to control the CMake source exactly and need to be able to work on air-gapped machines.
We have already a
cmake
copy installed and would like to use that when buildingpy-cmake
. The reason for that is that this allows packagers to maintain system- and compiler-specific patches and work-arounds for buildingcmake
itself in one location. The risk of version mismatch betweenpy-cmake
andcmake
is mitigated in such an environment, because we control the exact versions in Spack.Currently, we cannot point to an existing CMake binary install: we can only point to CMake sources or download CMake binaries.
The text was updated successfully, but these errors were encountered: