Replies: 1 comment
-
Yes. For the main directory approach, instead of patching it, you can use [tool.scikit-build]
minimum-version = "build-system.requires"
wheel.platlib = false
cmake.define.NB_TEST = false
[[tool.scikit-build.overrides]]
if.env.BUILD_TESTING = true
wheel.platlib = true
cmake.define.NB_TEST = true
cmake.define.NB_TEST_STABLE_ABI = true
cmake.define.NB_TEST_SHARED_BUILD = true Then you can set #697 has an example of the test directory approach. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I applied this patch to pyproject.toml:
and now I'm trying to run
cibuildwheel --only=cp312-pyodide_wasm32
. I needed to apply #693. After that it fails here:It seems that the
build/tests
directory only contains the following four files:cmake_install.cmake
,test_typing.py
,CMakeFiles
,libinter_module.s
'.I hit the same error when I do
cibuildwheel --only cp312-manylinux_x86_64
.@henryiii any idea what I should do here? Also, is it possible to make a
pyproject.toml
file in the test directory that instructs scikit-build to build from the parent directory? Or to have a second[tool.scikit-build.test]
set of options for scikit-build?Beta Was this translation helpful? Give feedback.
All reactions