As noted in my comment in the PR, this PR breaks the ROS build farm binaries by installing the libs to the wrong path. This seems like lib/x86_64-linux-gnu is the intended path from their PR but ROS needs simply lib for everything to line up correctly.
ament/ament_cmake#630 highlights potential ament solutions / fixes, but that is obviously going to be more time consuming than just fixing BT.CPP to use a more standard path as most users expect.
So my recommendation is to revert that user's PR and rerun bloom to get Lyrical / Rolling (and others) compiling libs to the right path so they can be used by binary installers. I see this issue in the testing repo binaries that if I symlink lib/x86_64-linux-gnu to lib then it works as expected -- but that's a hack just for me to get around the issue for my own lyrical release planning.
As noted in my comment in the PR, this PR breaks the ROS build farm binaries by installing the libs to the wrong path. This seems like
lib/x86_64-linux-gnuis the intended path from their PR but ROS needs simplylibfor everything to line up correctly.ament/ament_cmake#630 highlights potential ament solutions / fixes, but that is obviously going to be more time consuming than just fixing BT.CPP to use a more standard path as most users expect.
So my recommendation is to revert that user's PR and rerun bloom to get Lyrical / Rolling (and others) compiling libs to the right path so they can be used by binary installers. I see this issue in the testing repo binaries that if I symlink
lib/x86_64-linux-gnutolibthen it works as expected -- but that's a hack just for me to get around the issue for my own lyrical release planning.