On 05-04-2025 09:09, Elliott Sales de Andrade wrote:
The required CMake configuration for the build backend,
nanobind-config.cmake, is provided by python3-nanobind-devel. I think
that package should provide `cmake(nanobind)` as well, since using that
is what packaging guidelines recommend and it would make live easier to
find the required package.
The CMake files are in the Python package directory (because the
_Python_ packaging side is sandboxed), which is non-standard and
wouldn't be found by CMake. Thus it doesn't and shouldn't provide the
virtual name. If the Fedora packager patches it to install to a
standard location, then adding `cmake(nanobind)` would make sense (and
would automatically happen, too.)
I hadn't looked closely at the python-nanobind package yet. But I ran
into a very similar issue when packaging a project requiring nanobind.
In `pyproject.toml` `build-system` requires `nanobind`, which is simply
not enough for building against `nanobind`. So, I tried with using
`BuildRequires: cmake(nanobind)` first, which usually works in pulling
in the required devel package.
So, let me rephrase: pytho3-nanobind-devel should install CMake
configuration files in the standard location and provide `cmake(nanobind)`.
Also, upstream nanobind provides a small script to find the right
path; upstream openvdb should probably be suggested to use that:
$ python3 -c 'import nanobind; print(nanobind.cmake_dir())'
/usr/lib/python3.13/site-packages/nanobind/cmake
I think that's what should be used in nanobind-config.cmake "internally"
and returned to the package trying to find it.
-- Sandro
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
