-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install includes to include/${PROJECT_NAME} #184
Conversation
Signed-off-by: Shane Loretz <[email protected]>
Not sure what the cause of windows CI failing is. I'll come back and investigate
|
Windows failures aside, I'm good with the general idea of this. Though I would like to see a bunch of these types of PRs get merged at the same time, so I'd want to see more of the packages listed in ros2/ros2#1150 (comment) done before merging this. |
I would recommend trialing this on a small number of packages and releasing them to Rolling first. That would give early warning if there's a problem without having to work on and then revert a bunch of PRs |
All right, that's fair enough. By the way, the failing Windows build may have been unrelated to this PR and may have been fixed by ros2/rclcpp#1843 . So I'd recommend kicking it off again. |
Part of ros2/ros2#1150
Part of ament/ament_cmake#365
This installs includes to another package specific include prefix. This avoids include directory search order issues that can happen when overriding packages in a merged underlay workspace.
I also made it export a modern CMake target instead of old style CMake variables.