HACK: Allow resolution of current project's path at build time #326
Conversation
This file contains 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 was referenced Jul 4, 2023
Closed
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.
The cmake function
xacro_add_filesrunsxacroat build time. To resolve$(find current_package)within xacro files,xacrorelies on a properly configured ament package index. However, this index is only created after building, during installation.By manually prepending
AMENT_PREFIX_PATHwith the current project'sament_cmake_indexin thebuildfolder and symlinking the source folder into the correspondingsharefolder, I was able to work around this shortcoming. However, a fix in https://github.com/ament/ament_cmake would be definitely better.Partially fixes #325.
Resolution of packages during xacro-dependency lookup still doesn't work.