Skip to content

build: update WebRTC branch from 7977 to 8059 (M155) - #360

Merged
devopvoid merged 2 commits into
mainfrom
build/webrtc-8059
Oct 13, 2026
Merged

devopvoid merged 2 commits into
mainfrom
build/webrtc-8059

Conversation

@devopvoid

@devopvoid devopvoid commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Updates the native build from WebRTC branch-heads/7977 (M152) to branch-heads/8059 (M155).

  • Set webrtc.branch to branch-heads/8059 and update the build guide.
  • Use the Chromium Clang that 8059 pins (llvmorg-24-init-7747-g62397f8b-27) in the Linux CI builds.
  • Install Windows SDK 10.0.28000.0 in the Windows CI builds; 8059's toolchain pins it and gn gen fails without it. Local Windows builds need it too.
  • From M155 the factory uses the network thread as its worker thread when none is supplied; update the comment in PeerConnectionFactory.

- Set webrtc.branch to branch-heads/8059 and update the build guide.
- Use the Chromium Clang that 8059 pins (llvmorg-24-init-7747-g62397f8b-27)
  in the Linux CI builds.
- Install Windows SDK 10.0.28000.0 in the Windows CI builds; the Windows
  toolchain of 8059 pins it and gn fails without it.
- M155 uses the network thread as the worker thread when none is supplied,
  and support for a distinct worker thread is being removed; update the
  comment in the PeerConnectionFactory accordingly.
The libc++ of the Clang that 8059 pins no longer pulls it in through other headers, so the Linux builds failed.
@devopvoid
devopvoid merged commit 74ab80e into main Oct 13, 2026
24 checks passed
@devopvoid
devopvoid deleted the build/webrtc-8059 branch October 13, 2026 13:25
SendableMetatype added a commit to EduGeyser/webrtc-java that referenced this pull request Oct 15, 2026
Brings in the work upstream added from October 11 to 15: hardware video
codecs on every platform, through Media Foundation, VideoToolbox, VA-API
and NVDEC, with WebRTC built with H.265 (devopvoid#346 to devopvoid#348, devopvoid#352, devopvoid#353, devopvoid#356,
devopvoid#359, devopvoid#371 to devopvoid#377); HEVC and AV1 decoding in the media player, with
dav1d and Vulkan Video (devopvoid#331, devopvoid#345); encoded frame injectors (devopvoid#365);
receiver source changes and audio packet infos (devopvoid#366); audio codec
factories (devopvoid#340); network thread observers called on a callback thread
(devopvoid#364); screen capture with ScreenCaptureKit (devopvoid#354); Windows audio
devices that mix more than two channels (devopvoid#358); autoninja (devopvoid#357); and
the release channels of the docs site (devopvoid#361).

Fork-side adaptations:
- The factory keeps the CreatePeerConnectionFactory overload without a
  worker thread, and still switches device capture on the network
  thread. devopvoid#355 copies WebRTC's factory setup and has the audio module
  learn a worker thread, which only matters for a worker thread distinct
  from the network thread, and WebRTC is removing those. The audio codec
  factories and hardware codec switches of devopvoid#340 and devopvoid#359 go to that
  overload.
- WebRTC stays on a commit on main, so the move to branch 8059 (devopvoid#360)
  and its fixed clang package are left out.
- The data channels variant builds WebRTC without H.265 and without the
  extra targets, leaves out the audio codec factory bindings and
  addTransceiverOfType, and skips the new tests that need audio or
  video.
- dav1d is built against the sysroot on native Linux builds as well, as
  FFmpeg is. CI installs Meson for the full variant only, checks out the
  dav1d submodule, and adds its commit to the FFmpeg cache key. The
  fork's Windows SDK step stays, without upstream's second one.
- The release workflow records the docs' version in the tagged commit,
  as upstream's now does. The docs site still builds from main, since
  this fork publishes none.
- The Maven files stay deleted: Jetty is bumped in the version catalog,
  and the docs lockfile takes upstream's bumps on top of the fork's
  newer VitePress.
- The media module's README builds with Gradle.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant