In BaseBox.h, the include path for python_defs.h actually goes up one directory too high; this is obscured by the way pybind11 is included, but fails if a system pybind11 is used.
In ConfigInfo.h, direct relative paths to pybind11 headers are used, but cmake already includes the pybind11 include path, so standard paths can be used instead. This simplifies use of system pybind11 headers (by a one-line cmake change) where necessary, for example, to fit Debian packaging policies.
Neither change should have any effect on the normal build process.
In BaseBox.h, the include path for python_defs.h actually goes up one directory too high; this is obscured by the way pybind11 is included, but fails if a system pybind11 is used.
In ConfigInfo.h, direct relative paths to pybind11 headers are used, but cmake already includes the pybind11 include path, so standard paths can be used instead. This simplifies use of system pybind11 headers (by a one-line cmake change) where necessary, for example, to fit Debian packaging policies.
Neither change should have any effect on the normal build process.