scikit-build/cmake-python-distributions

There should be a cmake option to use pre-installed cmake

yurivict opened this issue · 4 comments

We already have cmake on FreeBSD.
Installing cmake againhas these problems:

  1. It causes conflicts withe cmake package
  2. It wastes CPU to build cmake when it is already present.

Please add a cmake option, for example USE_EXTERNAL_CMAKE, that would just launch 'cmake' assuming that it already installed.

Could you guarantee that the CMake version exactly matched the package version? How would you ensure that someone wouldn't try to distribute this "empty" wheel? Or that they versions would continue to be in sync, what if you update the system cmake but not this "empty" package?

Opt-in isn't as bad, but it's still problematic. And it's the wrong solution.

The correct solution is simple: don't request the cmake PyPI package if you already have provided CMake via a different mechanism. You wouldn't ask for conda-forge metadata to be included in FreeBSD, so why ask for PyPI metadata?

If it's because people are putting "cmake" in build-system.requires. then just disable verification. And request that they use a proper system like scikit-build-core or a wrapper around get_requries_for_build_wheel that checks for a system cmake before requesting PyPI cmake.

And this is a duplicate of #80.