Skip to content
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

Open
ax3l opened this issue Mar 7, 2022 · 0 comments
Open

Externally Controlled CMake Binaries #227

ax3l opened this issue Mar 7, 2022 · 0 comments

Comments

@ax3l
Copy link

ax3l commented Mar 7, 2022

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 building py-cmake. The reason for that is that this allows packagers to maintain system- and compiler-specific patches and work-arounds for building cmake itself in one location. The risk of version mismatch between py-cmake and cmake 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.

@ax3l ax3l changed the title Externally Controlled CMake Externally Controlled CMake Binaries Mar 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant