But I am not sure (I looked quite thoroughly, but not finding something 100% clear) about what exactly do I have to run after CEF rebasing which affects the CHROMIUM_BUILD_COMPATIBILITY.txt.
Is it an a gclient sync? gclient sync --no-hooks? gclient sync --no-hooks --with_branch_heads? or the same automate-git.py command for checkout - mine being (part of a do-all script):
- Code: Select all
python3 %ROOTDIR%\automate-git.py --url=%URL% --download-dir=%ROOTDIR% --branch=%CEF_BRANCH% --no-depot-tools-update --no-build --no-distrib --no-distrib-docs --no-distrib-archive --no-debug-tests --no-release-tests --with-pgo-profiles
and this will detect the Chromium hash change and run all the sync/hooks/etc. necessary?