Cristian Le

> That's a fair point. However, since we have lots of small tasks the scheduling is not a big concern for us. That argument is completely inversed. Because `ctest` is...

Looks promising :). I'll need to draw it out on a paper to follow it :sweat_smile: , I'll come back to you after that. At first glance, I think the...

On the overall structure of the files, I think it's a good skeleton to cover all the cases, we just need to cover the navigations within there. Just a few...

@vyasr sorry for taking so long to get to this. I have updated the PR and added a few more navigation cases that I was referring to last time. I...

`Cython` functionality is a bit [more convoluted](https://scikit-build-core.readthedocs.io/en/latest/getting_started.html#cmake-file), but this CMake project doesn't look too difficult to port. It would take me some time to setup the environment and find the...

Hmm this would be tricky because scikit-build-core would have to be made aware of the installation paths that are to be used outside of the `site-packages` and afaik it cannot...

> In terms of making scikit-build-core aware of installation paths, I do know that the CMake file-based API https://cmake.org/cmake/help/latest/manual/cmake-file-api.7.html can be used to interrogate installation paths. I don't know if...

It is tricky because you can have the opposite as well. There was an idea on `PEP639` about allowing gitignore style syntax, specifically the `!` operator.

Hitting this one again because setting `${SKBUILD_SCRIPTS_DIR}` breaks the `install(TARGETS EXPORT)`. For unix, isn't the `bin` directory relative path is known and in the same prefix as `lib(64)/python/site-packages`? I'm not...

> Actually, sk-build is able to identify such a situation: > > > 2024-09-14 09:09:38,634 - scikit_build_core - WARNING - Can't find a Python library, got libdir=None, ldlibrary=None, multiarch=None, masd=None...