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.
Public API Changes
None
Description
Get build to work on Ros2 Jazzy, Ubuntu 24.04.
There are some diffs applied to the cloned webrtc source code (first two bullet points below) I'm not sure how to best apply them in this PR. Maybe apply a patch after pulling the code or something...
Open problems:
webrtc/build/webrtc/src/rtc_base/third_party/base64/base64.h
: add#include <cstdint>
webrtc/build/webrtc/src/build/util/lastchange.py
: replaceutcfromtimestamp
withfromtimestamp
on L318RTC_DISALLOW_COPY_AND_ASSIGN
macro, so currently it's commented out. Edit: Found it and fixed.vision_opencv
and checked out7a47d35
, and renamed a few .h to .hpp - I'm not sure if that's needed though, and I forgot where I read that this is required. Edit: yeah, seems to be needed.#71
After launching:
The webserver launches fine and shows the available topics:
But when trying to establish a connection, it crashes.
Looks like Unified Plan semantics deprecated a few of the older APIs and the webrtc client need to be rewritten...
https://webrtc.org/getting-started/unified-plan-transition-guide
There's a document on how to migrate native C++ applications to Unified Plan, but I can't access the doc...
I found this page that maybe (?) contains a copy of the document https://blog.csdn.net/dotphoenix/article/details/107480133 but no idea.