Remove unused boost dependency; OpenUSD vendors its own pxr_boost - #32
Conversation
|
@traversaro I think this PR should be merged before the TBB 2023 one to increase compatibility. |
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe/recipe.yaml:
For recipe/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/27931669399. Examine the logs at this URL for more detail. |
869b4b9 to
23e4ef5
Compare
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/27934297156. Examine the logs at this URL for more detail. |
|
Thanks! I am probably missing something, if boost is not used, can't we just remove the libboost-devel dependency instead of ignoring its run_exports ? |
OpenUSD 24.11+ replaced boost::python with a vendored, namespace-mangled pxr_boost and no longer links external boost in the default build. This recipe enables only PXR_ENABLE_PYTHON_SUPPORT (no OpenVDB/OpenImageIO), so nothing links libboost: all boost symbols resolve to the in-package libusd_boost, and the remaining <boost/...> includes in public headers are behind opt-in guards (PXR_BOOST_PYTHON_HAS_BOOST_SHARED_PTR, PEGTL's legacy-compiler fallback). Keeping libboost-devel in host only leaked a spurious `libboost` run-export, pinning openusd into every boost migration and forcing downstream consumers (usd-exchange, FreeCAD) onto openusd's boost version. Removing it drops the phantom runtime constraint and takes openusd out of the boost migration cycle.
…2026.06.21.23.35.32 Other tools: - conda-build 26.5.0 - rattler-build 0.66.2 - rattler-build-conda-compat 1.4.15
23e4ef5 to
784f058
Compare
|
I wasn't 100% sure Boost wasn't used, but it's not exported and therefore doesn't require compatibility in depending projects. I've removed it altogether in the latest force push. Hopefully it will build and pass tests. |
|
It seems that indeed (non vendored/forked) boost is not used at all! |
OpenUSD 24.11+ replaced boost::python with a vendored, namespace-mangled pxr_boost and no longer links external boost in the default build. This recipe enables only PXR_ENABLE_PYTHON_SUPPORT (no OpenVDB/OpenImageIO), so nothing links libboost: all boost symbols resolve to the in-package libusd_boost, and the remaining <boost/...> includes in public headers are behind opt-in guards (PXR_BOOST_PYTHON_HAS_BOOST_SHARED_PTR, PEGTL's legacy-compiler fallback).
libboost-devel is kept in host for the build, but its run-export is ignored since the built libraries link only the vendored libusd_boost, never external libboost. (Note: this still leaves openusd subject to boost-migration rebuilds, which become no-ops.) Bump build number for the rebuild.
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)