On 2025-04-05 03:34, Vitaly Zaitsev via devel wrote:
On 05/04/2025 00:45, Luya Tshimbalanga wrote:
Trying to set "nanobind_DIR" does nothing. Can someone look at the
issue?
Just add -DCMAKE_PREFIX_PATH='%{python3_sitelib}/nanobind/cmake' to
%cmake macros.
I am confirming using
"-DCMAKE_
On 05/04/2025 00:45, Luya Tshimbalanga wrote:
Trying to set "nanobind_DIR" does nothing. Can someone look at the issue?
Just add -DCMAKE_PREFIX_PATH='%{python3_sitelib}/nanobind/cmake' to
%cmake macros.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
--
___
On Sat, Apr 5, 2025 at 3:51 AM Sandro wrote:
>
> On 05-04-2025 09:32, Sandro wrote:
> >> 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())'
> >> /us
On 05-04-2025 09:32, Sandro wrote:
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
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
On Sat, Apr 5, 2025 at 3:00 AM Sandro wrote:
>
> On 05-04-2025 00:45, Luya Tshimbalanga wrote:
> > Hello team,
> >
> > I hit an issue when building openvdb on nanobind dependency which refuses
> > to use python3-nanobind at the following:
> >
> > -- Found Python: /usr/bin/python3.13 (found versio
On 05-04-2025 00:45, Luya Tshimbalanga wrote:
Hello team,
I hit an issue when building openvdb on nanobind dependency which refuses to
use python3-nanobind at the following:
-- Found Python: /usr/bin/python3.13 (found version "3.13.2") found components:
Development Interpreter Development.Mod
