-
Notifications
You must be signed in to change notification settings - Fork 21
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
Jazzy Jalisco #337
base: main
Are you sure you want to change the base?
Jazzy Jalisco #337
Conversation
This also needs updates to the readme |
I can do that. Do we want to replace the examples in the README from Humble->Jazzy? Since Jazzy is the newest long term support? I know that we're still supporting Humble, but I just figured that we'll want to point new users to install Jazzy instead. Or do we want to keep Humble as the example distro for some time/does it not matter? |
I think so. |
I added Jazzy to the README. I replaced Humble with Jazzy in the example commands. I did not remove any references to Foxy or Galactic. I also removed a dead link to ROS Answers. I see discussion here that an archive of ROS Answers is being created. I can add back the link if that is later made available. |
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.
Couple humble references remain:
Lines 162 to 163 in 0dcf5a6
$ md5sum -b mr2_yrc1_h.out | |
e2d088b765a0bfed501aa213a1be1de0 mr2_yrc1_h.out |
Line 490 in 0dcf5a6
source /opt/ros/humble/setup.bash |
Also, this table needs to be updated:
Lines 169 to 179 in 0dcf5a6
|**Controller** |**ROS 2 Version** | **File** |**Version** | **MD5 hash** | | |
|:--------------|:-----------------|:------------------|:-----------|:-----------------------------------| | |
| DX200 | Foxy | `mr2_dx2_f.out` | `0.1.3` | `a9a9e10403f726062c25d97654fad316` | | |
| DX200 | Galactic | `mr2_dx2_g.out` | `0.1.3` | `e8db7512215da240b28b985f2f2af98b` | | |
| DX200 | Humble | `mr2_dx2_h.out` | `0.1.3` | `611bda537655cf8a60d85600da6043f4` | | |
| YRC1000 | Foxy | `mr2_yrc1_f.out` | `0.1.3` | `84bfb44e2043372127d9dfc1157a79b5` | | |
| YRC1000 | Galactic | `mr2_yrc1_g.out` | `0.1.3` | `866e090b6c724429ce03117712c951f4` | | |
| YRC1000 | Humble | `mr2_yrc1_h.out` | `0.1.3` | `e2d088b765a0bfed501aa213a1be1de0` | | |
| YRC1000micro | Foxy | `mr2_yrc1m_f.out` | `0.1.3` | `027e77b427a212aa63e5d7962d48ad92` | | |
| YRC1000micro | Galactic | `mr2_yrc1m_g.out` | `0.1.3` | `042d753a7729784fec8c5c23bef3e685` | | |
| YRC1000micro | Humble | `mr2_yrc1m_h.out` | `0.1.3` | `c0e61adbf5bf6fd6a734211f15bb0f0a` | |
I added some more humble->jazzy swaps in the documentation. I don't know how I missed so many the first time around. We will still have to update the table with the new versions/hashes once they are ready. |
555289b
to
a2a5ca9
Compare
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.
Round of comments
I've addressed those changes. The project filters are particularly annoying to deal with, visual studio likes to change things in the background. |
@jimmy-mcelwain: the PR adding Iron support (#303) added these lines to the Are they no longer needed? Were we doing something wrong previously? Or is this a difference between Iron and Jazzy (in our favour for once)? (the Arduino examples also don't seem to include them: Iron version, Jazzy version) |
They are no longer needed. It is a difference between Iron and Jazzy in our favor. In Jazzy, the I assume that the Arduino never includes them because the |
What do we still have to do for release? I think that this repo should be good, except for we could clean up the commit history/rebase and update the table with new hashes. But first Yaskawa-Global/micro_ros_motoplus#11 needs to be reviewed. |
This passes all my testing. We just need to finish merging the back-end stuff.
Not necessary until we make the 0.2.0 release. |
libyaml_vendor being installed by ament_cmake_vendor_package (a new change in jazzy) puts it in a different location than previously.
rclc_timre_init_default was replaced with rclc_timer_init_default2 in jazzy, which has a different set of parameters. The old function is now deprecated, this change gets rid of the message.
Also change the distro used in examples from Humble to Jazzy, and remove dead links (ROS Answers)
The buildscript has been changed so that vendor packages will have their name in the include path, matching non-vendor packages.
Distributions older than Jazzy place vendor packages with the rest of the source files, but Jazzy places them in the opt directory, so the build script places the include files somewhere else.
A link to a ROS Answers thread was removed after ROS Answers was taken offline, but now the archive is up so we can add the old link back. Co-authored-by: G.A. vd. Hoorn <[email protected]>
1a7ea52
to
89f87b7
Compare
thanks for rebasing @jimmy-mcelwain. This now builds because conditionals were added in ee58dda and 7facc1d. At least this introduced no regressions. |
(pre)released Should succeed, but let's see. Edit: made a mistake. Will fix in a bit. |
911b2c5
to
7a9889c
Compare
See #333. This updates MotoROS2 to make it compatible with Jazzy Jalisco, the new long term support release of ROS2.