Having looked into this a bit further, it appears the new hotness is
that this is actually being handled in the Boost-shipped CMake module:
/usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake
>From my read of that, the expectation *now* is that you just do:
find_package(Boost COMPONENTS python)
And it does the right thing. But of course this approach breaks any
package which was intentionally using "python3" in previous releases, or
building libraries for both Python 2 and 3. In summary, these are how to
link to boost_python over the past four years:
1. find_package(Boost COMPONENTS python)
2. find_package(Boost COMPONENTS python-pyXY)
3. find_package(Boost COMPONENTS pythonX)
4. find_package(Boost COMPONENTS pythonX-pyXY)
5. find_package(Boost COMPONENTS pythonXY)
Xenial was 1 and 2. Bionic was 1, 2, 3, and 4. Focal is now 1 and 5, but
1 is now Python 3 instead of 2.
This is insane.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865209
Title:
Boost 1.71 missing python3/numpy3 symlinks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.71/+bug/1865209/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
