I am attempting to build branch 7871 using the "Automated Method" on Windows. While I was able to build 7871 successfully around July 25th, I am currently encountering two issues during the sync/build process with the latest codebase.
---
### Issue 1: Git LFS Error during `gclient sync`
During `gclient sync` (or `automate-git.py`), Git LFS encounters an issue when checking out or downloading binary assets, resulting in errors similar to:
- Code: Select all
________ running 'git reset --hard 9eedac0510c52e2014d54a2d1112d96c00d0adc2 --quiet' in 'f:\code\chromium_git\chromium\src\third_party\litert\src'
[0:00:49] Downloading litert/prebuilt/android_arm32/libLiteRt.so (3.5 MB)
[0:00:49] Error downloading object: litert/prebuilt/android_arm32/libLiteRt.so (382978a): Smudge error: Error downloading litert/prebuilt/android_arm32/libLiteRt.so (382978af0bb38b901ca8a8a49de8d2e7747b7a6ea617cea3c22d225a824f9af3): batch response: Client error https://chromium.googlesource.com/external/github.com/google-ai-edge/LiteRT.git/info/lfs/objects/batch from HTTP 405
[0:00:49] Errors logged to 'F:\code\chromium_git\chromium\src\third_party\litert\src\.git\lfs\logs\20260803T182659.3597955.log'.
[0:00:49] Use `git lfs logs last` to view the log.
[0:00:49] error: external filter 'git-lfs filter-process' failed
[0:00:49] fatal: litert/prebuilt/android_arm32/libLiteRt.so: smudge filter lfs failed
----------------------------------------
Error: Command 'git reset --hard 9eedac0510c52e2014d54a2d1112d96c00d0adc2 --quiet' returned non-zero exit status 128 in f:\code\chromium_git\chromium\src\third_party\litert\src
Downloading litert/prebuilt/android_arm32/libLiteRt.so (3.5 MB)
Error downloading object: litert/prebuilt/android_arm32/libLiteRt.so (382978a): Smudge error: Error downloading litert/prebuilt/android_arm32/libLiteRt.so (382978af0bb38b901ca8a8a49de8d2e7747b7a6ea617cea3c22d225a824f9af3): batch response: Client error https://chromium.googlesource.com/external/github.com/google-ai-edge/LiteRT.git/info/lfs/objects/batch from HTTP 405
Errors logged to 'F:\code\chromium_git\chromium\src\third_party\litert\src\.git\lfs\logs\20260803T182659.3597955.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: litert/prebuilt/android_arm32/libLiteRt.so: smudge filter lfs failed
Traceback (most recent call last):
File "F:\code\automate\automate-git.py", line 1568, in <module>
run("gclient revert --nohooks", chromium_dir)
File "F:\code\automate\automate-git.py", line 174, in run
return subprocess.check_call(
^^^^^^^^^^^^^^^^^^^^^^
File "F:\code\depot_tools\bootstrap-2@3_11_8_chromium_35_bin\python3\bin\Lib\subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['gclient', 'revert', '--nohooks']' returned non-zero exit status 1.
---
### Issue 2: Build failure in Rust `hb_rs_generator` (Drive Cross-Path Error)
When running `autoninja -C out/Release_GN_x86 cefclient`, the build fails at the `hb_rs_generator` step with a relative path calculation error across drives:
- Code: Select all
FAILED: ./gen/third_party/harfbuzz/hb_rs_generator/hb.rs ACTION //third_party/harfbuzz:hb_rs_generator
err: error in depfile "out/Release_GN_x86/obj/third_party/harfbuzz/hb_rs_generator.d": failed to make workspace relpath "C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.26100.0\\shared\\winapifamily.h": Rel: can't make C:\Program Files ... relative to F:\code\chromium_git\chromium\src
```
Environment:
Chromium/CEF Source: Located on drive `F:\` (`F:\code\chromium_git\chromium\src`)
Windows SDK: Located on drive `C:\` (`C:\Program Files (x86)\Windows Kits\...`)
Target: `x86` (Release)
It appears that `bindgen` (or Siso) fails when trying to compute a relative path between two different drives (`C:\` and `F:\`) for the generated `.d` depfile.
---
### Questions:
1. Is setting `enable_rust = false` in `args.gn` the recommended workaround for CEF builds when source and SDK are on different drives, or is there a preferred flag/configuration for this in recent CEF 7871 builds?
2. Are there any recent updates to depot_tools / LFS hooks that might be causing the Git LFS issue?
Any guidance or recommended fixes would be greatly appreciated.
Thanks!