Replies: 1 comment 1 reply
-
This is currently solved in scikit-build-core via config-settings options:
There's no matching system for the setuptools plugin yet; developing that will likely affect what scikit-build classic will adopt (since it will move to using that). Setuptools has the annoying feature of requiring an extra layer on config settings options (global-option and such).
And to point 1): |
Beta Was this translation helpful? Give feedback.
-
Short Question
Is it possible to pass through command-line options from
pip install
to CMake viascikit-build
without using environment variables?More Details
I'm working on migrating a CMake-based project that uses
setuptools
+setup.py
+ subclassing of stuff from stuff fromsetuptools.command
to a PEP517/PEP518 compliant build.Because the project relies on CMake to build its C/C++ shared library, I'd like to use
scikit-build
for this.Today, the project supports passing custom arguments through
pip install
to change the library compiled when building from an sdist.For example,
becomes a command like the following executed by a
subprocess.check_call()
call insetup.py
I'd like to achieve similar behavior using
scikit-build
.I've seen https://scikit-build.readthedocs.io/en/latest/usage.html#cmake-configure-options, which suggests that one can set a
CMAKE_ARGS
environment variable.I'd like to avoid recommending that to users of my project, because:
scikit-build
projectsCMAKE_ARGS
environment variable is unexpected #722Specific project I'm working on:
setup.py
: https://github.com/microsoft/LightGBM/blob/87e3c0d9ba81ee229dedeaac10765054c25b5284/python-package/setup.pyNotes for Reviewers
I hope I'm in the right place (assumed based on #800 that this Discussions board is the preferred place to post questions like this).
Thanks for your time and considerations, and for this awesome project!
Beta Was this translation helpful? Give feedback.
All reactions