-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Suggest adding exec_depend on ros2launch for packages with launch files #1786
Suggest adding exec_depend on ros2launch for packages with launch files #1786
Conversation
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 think this is a good note to add. I agree it's not clear where to put it. What would you think about adding it at the end of the setup section in the creating launch files tutorial?
I don't really mind, but this tutorial mostly shows how to create a standalone launch file so it feels kind of rushed to mention this at the very beginning. There's a note that mentions having a launch file under a specific package here: https://docs.ros.org/en/rolling/Tutorials/Launch-Files/Creating-Launch-Files.html#ros2-launch. What do you think about putting this new note after that one? |
… files Signed-off-by: Christophe Bedard <[email protected]>
5448d6b
to
3b3b843
Compare
Sorry to fall off. That sounds good to me. I think this spot is better because it comes into the user's awareness sooner than later. |
Signed-off-by: Christophe Bedard <[email protected]>
Signed-off-by: Christophe Bedard <[email protected]>
@Mergifyio backport galactic foxy |
…es (#1786) * Suggest adding exec_dependency on ros2launch for packages with launch files Signed-off-by: Christophe Bedard <[email protected]> * Move note to 'Creating a launch file' tutorial Signed-off-by: Christophe Bedard <[email protected]> * Add link to launch file formats guide Signed-off-by: Christophe Bedard <[email protected]> (cherry picked from commit 622a1a5)
…es (#1786) * Suggest adding exec_dependency on ros2launch for packages with launch files Signed-off-by: Christophe Bedard <[email protected]> * Move note to 'Creating a launch file' tutorial Signed-off-by: Christophe Bedard <[email protected]> * Add link to launch file formats guide Signed-off-by: Christophe Bedard <[email protected]> (cherry picked from commit 622a1a5)
✅ Backports have been created
|
…es (#1786) (#2138) * Suggest adding exec_dependency on ros2launch for packages with launch files Signed-off-by: Christophe Bedard <[email protected]> * Move note to 'Creating a launch file' tutorial Signed-off-by: Christophe Bedard <[email protected]> * Add link to launch file formats guide Signed-off-by: Christophe Bedard <[email protected]> (cherry picked from commit 622a1a5) Co-authored-by: Christophe Bedard <[email protected]>
…es (#1786) (#2139) * Suggest adding exec_dependency on ros2launch for packages with launch files Signed-off-by: Christophe Bedard <[email protected]> * Move note to 'Creating a launch file' tutorial Signed-off-by: Christophe Bedard <[email protected]> * Add link to launch file formats guide Signed-off-by: Christophe Bedard <[email protected]> (cherry picked from commit 622a1a5) Co-authored-by: Christophe Bedard <[email protected]>
Thanks for the PR, @christophebedard! |
This is a change suggested here after we realized that the launch frontends may not get built if your
package doesn't depend on them (almost none of the common CLI/launch packages do): ros2/launch#516 (comment)
Note that the last line in this proposed change isn't currently valid. Depending on
ros2launch
will only ensurelaunch_xml
/launch_yaml
are built after this PR (or an equivalent PR) is merged: ros2/launch_ros#256I couldn't really find a perfect place to put this note, but this seemed like an okay spot.
Signed-off-by: Christophe Bedard [email protected]