dolfin doesn't find the pybind11 module during the build, however it has
a build-dependency on that. So I assume that it is meant to do
something senseful with that build-dependency.
The build still succeeds, so maybe add a check that some artifacts added
with that component show up in the packages?
[...]
-- Detecting CXX compile features - done
Traceback (most recent call last):
File "<string>", line 1, in <module>
import pybind11; print(pybind11.get_cmake_dir())
^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'pybind11'
CMake Warning (dev) at
/usr/lib/cmake/pybind11/FindPythonLibsNew.cmake:101 (message):
Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs
modules
are removed. Run "cmake --help-policy CMP0148" for policy details. Use
the cmake_policy command to set the policy and suppress this warning, or
preferably upgrade to using FindPython, either by calling it explicitly
before pybind11, or by setting PYBIND11_FINDPYTHON ON before pybind11.
Call Stack (most recent call first):
/usr/lib/cmake/pybind11/pybind11Tools.cmake:44 (find_package)
/usr/lib/cmake/pybind11/pybind11Common.cmake:243 (include)
/usr/lib/cmake/pybind11/pybind11Config.cmake:257 (include)
CMakeLists.txt:28 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.
CMake Deprecation Warning at
/usr/lib/cmake/pybind11/FindPythonLibsNew.cmake:110 (cmake_policy):
The OLD behavior for policy CMP0148 will be removed from a future version
of CMake.
The cmake-policies(7) manual explains that the OLD behaviors of all
policies are deprecated and that a policy should be set to OLD only under
specific short-term circumstances. Projects should be ported to the NEW
behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
/usr/lib/cmake/pybind11/pybind11Tools.cmake:44 (find_package)
/usr/lib/cmake/pybind11/pybind11Common.cmake:243 (include)
/usr/lib/cmake/pybind11/pybind11Config.cmake:257 (include)
CMakeLists.txt:28 (find_package)