-
Notifications
You must be signed in to change notification settings - Fork 143
feat: add option to export libraries as cmake targets #455
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
Open
VRichardJP
wants to merge
2
commits into
ament:rolling
Choose a base branch
from
VRichardJP:ament_ex_backport
base: rolling
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@VRichardJP I know you said you don't have the ability to test this and that you've moved on, but if you have the time and context still, does this conditional install need to be outside of the above if-else?
As I read the code, one thing that definitely changed is that we try to install
${${PROJECT_NAME}_TARGETS}even if you don't useEXPORT_LIBRARY_TARGETS. If we were able to move this block up into theif (_ARG_AMENT_AUTO_PACKAGE_EXPORT_LIBRARY_TARGETS)clause, then this change becomes a very safe one (EXPORT_LIBRARY_TARGETSgives you a new behavior and without it you get the old behavior as the default).But if you think it needs to be outside the clause then I'll have to study it closer. I don't think anything else is using
${${PROJECT_NAME}_TARGETS}, but I need to spend more time on it.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand your point.
As I look back at the code, I think I have implemented it this way because it is simply more future proof. If you consider that more scripts may add targets to
${PROJECT_NAME}_TARGETSin the future (e.g. binaries as target too), and that targets should only be exported once (if any), then I think it makes more sense to keep the target exports separate.Basically, this PR adds support for target export, and uses that new feature to implement a new export library as target option.