Export Threads dependency - #63
Merged
Merged
Conversation
Signed-off-by: David Laseca Perez <davidlaseca@eprosima.com>
|
Tick the box to add this pull request to the merge queue (same as
|
Author
|
@mergify backport lyrical |
✅ Backports have been createdDetails
|
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
2 participants
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.
Description
The Threads dependency added in ros2#579 and gated in #56 causes errors in consumers because they cannot resolve the Threads::Threads target in the static micro-ROS build. Because of this type of build, CMake forwards the
PRIVATE Threads::Threadsto the consumers, which makes it appear inrcutilsExport.cmakebut undefined sinceThreadswas not exported.This PR solves this by exporting the target when the build needs it (
RCUTILS_NO_THREAD_SUPPORT=OFF).