fix: expose compat headers through the sas_core INTERFACE target - #13
Merged
Merged
Conversation
The INTERFACE target forwarded to marinholab::sas::core + Eigen but never declared its own include directories, so the compat headers (include/sas_core/*.hpp) were not on the include path of downstream packages linking sas_core::sas_core. Downstream packages doing #include <sas_core/...> failed with: fatal error: sas_core/eigen3_std_conversions.hpp: No such file or directory. Add BUILD_INTERFACE/INSTALL_INTERFACE include dirs so they propagate in both workspace and installed use. Co-authored-by: openhands <openhands@all-hands.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Fixes a build break in the thin wrapper that only shows up when downstream ROS packages are compiled against it — the wrapper's own smoke test (standalone
g++with explicit-I) did not catch it.Problem
The wrapper's
sas_coreis a pureINTERFACElibrary:It forwards to the core target but never declares its own include directories. The
install(DIRECTORY include/)line installs the compat headers (include/sas_core/*.hpp), but installing a file does not put it on the include path of consumers — that comes from the target's interface. Previously the monolithic package provided those headers for free through its realsas_core_purelibrary.Result — the first
colcon buildof a downstream package against the wrapper fails (observed in the PPA builder run onsmart_arm_stack_ROS2lyrical, and reproduced locally):Affected downstream packages (all include
<sas_core/...>headers):sas_conversions,sas_common,sas_datalogger,sas_robot_driver,sas_robot_kinematics.Fix
Standard ament pattern — expose the compat headers through the INTERFACE target for both workspace and installed use:
Verification
Reproduced and verified in the exact environment (
murilomarinho/sas:jazzydocker image,.debinstalled, as the CI/builder uses):colcon buildofsas_core+ downstreamsas_conversions→fatal error: sas_core/eigen3_std_conversions.hpp: No such file or directory(exit 2)2 packages finished, exit 0Note for the PPA build
Once this is merged, re-run the
sas deb builderworkflow (smart_arm_stack_ROS2) — the run 35702346871 failed at exactly this step (colcon build→sas_conversions); thelibmarinholab-sas-corebuild itself was green (v26.09.08).This pull request was created by an AI agent (OpenHands) on behalf of the repository owner.