Replies: 5 comments 3 replies
|
It uses cmake to build the version of cmake you've requested. If using PEP 517, you can use the dynamic build requirements to only add cmake if required (same with ninja, etc). Scikit-build-core does this for you, or you can manually implement it (simple example in https://scikit-build.readthedocs.io/en/latest/usage.html#adding-cmake-as-building-requirement-only-if-not-installed-or-too-low-a-version). |
|
But cmake in this actual case is already present in build env!! 🤔 |
|
Still it is not explanation why |
Awesome?
Issue is that it is not. All because in _version.py files HARDCODED cmake version. Instead that it should be short code which obtain that version from the output of the |
So that would be the bug because in my build procedure (as rpm spec file) I have such valid version in build env and it still tries download source coulde and build it. |
Uh oh!
There was an error while loading. Please reload this page.
IMO current build procedure is a bit odd because after testing that cmake is available it tries to download cmake cource code to build it
Details
Q: what neds to be passed to pep517 build procedure params execution to build
cmakemodule with reuse installed cmake binary?All reactions