Skip to content

yuv-sys: actionable error when libyuv submodule is not initialized - #1347

Open
zacha7214 wants to merge 3 commits into
livekit:mainfrom
zacha7214:main
Open

yuv-sys: actionable error when libyuv submodule is not initialized#1347
zacha7214 wants to merge 3 commits into
livekit:mainfrom
zacha7214:main

Conversation

@zacha7214

Copy link
Copy Markdown

Problem

A fresh git clone without --recursive leaves yuv-sys/libyuv empty. The build script copies the empty directory and fails several calls later with:

thread 'main' panicked at yuv-sys/build.rs:140:10:
called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }

Nothing in the error points at the submodule as the cause, and the README build instructions don't mention --recursive. CI/container builds don't hit this because the Dockerfile initializes submodules explicitly — it only affects local builds from a fresh clone.

Fix

Check for libyuv/include/libyuv.h before the copy and panic with the remedy.

Verification

  • git submodule deinit -f yuv-sys/libyuv → build fails with the new message
  • git submodule update --init → clean build succeeds (macOS, aarch64)

Added a check to ensure the libyuv submodule is initialized before proceeding.
@zacha7214
zacha7214 requested a review from ladvoc as a code owner August 22, 2026 22:24
@CLAassistant

CLAassistant commented Aug 22, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

devin-ai-integration[bot]

This comment was marked as resolved.

zacha7214 and others added 2 commits August 22, 2026 16:48
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
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.

2 participants