Installation instructions #1526
Assignees
Comments
|
I'd like to give this a go on Windows 10 22H2 |
|
The Install OpenSSL section has an issue in the instructions:
Shining Light Productions currently only offers versions Would using |
Ah, that is a good question. I didn't realize they stopped offering the 1.X series. I think the 3.X series should work. I'm going to suggest you go ahead and try out the latest (3.3.0), and see if it builds and works. If so, we can update the documentation. |
|
Putting this here for reference: ros2/ros2_documentation#2878 |
|
Separate issue has occurred. Error building Perhaps an issue with CMake configuration repo version |
OK, it turns out that there was a bug in CMake that will not allow OpenSSL 3.3 packages to work. It was fixed at the beginning of April in Kitware/CMake@aa86f48 , and there is a new release (3.29.2) that includes it. So I think what we probably need to do here is to switch to installing OpenSSL 3.3.0 via chocolatey in the installation instructions. That will also mean we need to update CMake to at least 3.29.2. And finally, we'll have to update CI so that it does the same thing we are instructing users to do. I'll get started on making all of that happen, it will take a few hours. |
|
Not sure it's relevant but want to highlight that there's an OpenSSL binary provided at https://www.zlatkovic.com/pub/libxml/64bit/ currently at v1.0.2e if it's preferable to not use a newer version. |
8 tasks
|
I just wanted to leave an update here to say we have been working on the issue. To fix this properly, we are going to have to do a number of upgrades, at least:
(I also think it is likely we'll need one or two more PRs) We'll keep working through this in the next couple of days. |
|
All right. It turned out that due to various other problems, we couldn't actually update to OpenSSL 3.3.0 on Windows (though this is something we are going to look at for post-Jazzy). Instead, we actually switched both our CI and the instructions to install OpenSSL 1.1.1 from chocolatey, which is exactly what people did to workaround this issue during testing. With that, I'm going to close this out as done. Thanks for testing and the patience here, all. Going ahead and closing this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow the official installation instructions for the platform. If instructions have not been published for the platform, use the instructions for Rolling Ridley.
For source build platforms, this includes the installation of dependencies and building the packages.
Configuration
Links
Process
Install works
The text was updated successfully, but these errors were encountered: