Cristian Le

> > hard-coding a hint for that package > > Just to be clear, are you referring to the build dependency https://pypi.org/project/pkgconf/? Originally the `pkgconfig`, but the same applies for...

Try to add `SKBUILD_LOGGING_LEVEL: "DEBUG"` env var to get some more debug logs

Argh, windows is always a challenge. The `CMAKE_PREFIX_PATH` is as we would expect. ``` 2025-10-26 11:17:54,917 - scikit_build_core - DEBUG - SITE_PACKAGES: C:\Users\runneradmin\AppData\Local\Temp\build-env-9dei9xy0\Lib\site-packages ``` But the executables are installed in...

> I don't know enough about scikit-build-core or CMake to find where to add the above code. The snippet above can fit just before the `find_package(PkgConfig)`. > It might be...

> You could also combine it in: `cmake/SetSystemLibIfExists.cmake` Not quite. It *must* be before the `find_package(PkgConfig)`, but that could be moved there also. > The whole `verify_shared` flow was added...

> but I think that the issue may arise when we build coincurve on conda-forge - I don't remember But conda CI has a whole different workflow file that doea...

> I don't understand what you mean by "conda-forge CI for upstream". There are scripts in the conda-forge that make the build differ between the build instructions in upstream and...

Oh, my bad, that is indeed the case. I was looking at the top-right section where it was indicating that it points to the tag `v3.1.0`. Could that part be...

> Oh that is a feature of [mkdocs-material](https://squidfunk.github.io/mkdocs-material/) theme, showing the newest github tag. Isn't it configurable to specify if it should show the current branch or the latest version...

Might need to revisit this with the context of #4297. I guess main thing to figure out is how do we define which repo or git forge it is coming...