mcap_vendor: only install public headers#1207
Merged
james-rms merged 1 commit intoros2:rollingfrom Dec 13, 2022
Merged
Conversation
a3e07a3 to
3d20e25
Compare
Signed-off-by: James Smith <james@foxglove.dev>
3d20e25 to
31eea07
Compare
emersonknapp
approved these changes
Dec 12, 2022
Contributor
Author
|
Gist: https://gist.githubusercontent.com/james-rms/7429ad7cf59cee8627d00c71cb515b53/raw/527f75d0ec19b0a45c5b2935773a9dc818bd47b3/ros2.repos |
Contributor
Author
|
@mergify backport humble |
✅ Backports have been createdDetails
|
mergify bot
pushed a commit
that referenced
this pull request
Dec 14, 2022
Signed-off-by: James Smith <james@foxglove.dev> (cherry picked from commit 98ec717)
emersonknapp
pushed a commit
that referenced
this pull request
Dec 28, 2022
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.
Right now:
The upshot is that we're installing implementation files (
.inl) into the user's ROS workspace where they could find themselves including them by accident. An example of what could go wrong is:They might try to work around this by installing
liblz4-dev, which would cause their program to compile but may cause linking issues down the road, since the installedlibmcap.sois compiled with lz4 statically linked in, potentially a different version as well.Testing
bloom-generate rosdebianthat only.hppfiles are installed to the debian