Successful Builds Since 2022? #402
Comments
|
What do you mean by "from scratch"? Our CI builds every release from source as well as the maintainers for testing |
|
Or did you confuse this repo with the following: https://github.com/macchrome/winchrome |
|
Yes, I understand what the CI does. Though it seems the dependencies are having difficulty working together which I see a lot when something isn't quite maintained over a couple years. I've been through the typically seen build errors here, esbuild, rust, directx, then back to rust, now clang. The inconsistency I find very odd. I've tried in the Visual Code terminal, also cmd terminal all as user and as administrator. Just odd. Last night was my closest and made it to the ninja building. But a las dead in the water. -- snipped -- |
smblogger
changed the title
|
Probably time to start updating things requiring python 3.10. What I meant by from scratch is from clean directory and Git to the "First-time setup" forward. Re-running under the previous setup environment is probably doing fine for you guys. I think the issue is python 3.10 vs 3.12. Rust is outdated now too. Many of the tools in the "python3 ungoogled-chromium\utils\clone.py -o build\src" segment are cloning themselves and installing with python3.12 so lets hope those have back compatibility with 3.10. MSYS2 MSYS "pacman -S quilt python3 vim tar dos2unix" will no longer install 3.10. Forces to 3.12. So then the patch checks fail, probably related. $ source devutils/set_quilt_vars.sh ++++ readlink -f ./devutils/check_patch_files.sh
Meanwhile back in Cmd INFO: Unpacking "esbuild" to third_party/devtools-frontend/src/third_party/esbuild ... Then more errors out of various others as mentioned before. To reproduce all of this try it on a clean setup using those first time setup instructions. And why it's complaining about file already exists above i have no clue since it was a cleared build/src folder. Everything is just going to hell in a handbasket. Cleaned src and build.py again........... warning: trait warning: C:\Users\Wil\WebApps\ChromiumBrowser\buildone\ungoogled-chromium-windows\build\src>exit C:\Users\Wil\WebApps\ChromiumBrowser\buildone\ungoogled-chromium-windows\build\src>set DEPOT_TOOLS_WIN_TOOLCHAIN=0 C:\Users\Wil\WebApps\ChromiumBrowser\buildone\ungoogled-chromium-windows\build\src>"third_party\ninja\ninja.exe" "-C" "out\Default" "chrome" "chromedriver" "mini_installer" |
|
I set up a new build machine a few months ago following the steps described in the README and it worked fine. The rust version used during the build process is derived from the version google uses in their build (as described in the README). Most of the python scripts used are part of the You are completely right, python 3.10 is outdated. But so are a lot of the tools downloaded and used during the build process. We only update those downloads when needed and that's also true for the python version used. (That's why there is a build-in python version check in the build script so that we don't have to debug errors caused by an unsupported python version) I noticed your checkout path is quite long/nested. Try moving the checked out folder to the root of your disk and check if this helps. |
|
Yes. I did notice that one of the ninja/clang tests was failing and it dawned on me before reading above reply. I commented out that test line for now and ran ninja again and sure enough, it's still compiling. 250 characters exactly in my long path as you mentioned. ninja: error: win_clang_x64_for_rust_host_build_tools/toolchain.ninja:126: loading 'win_clang_x64_for_rust_host_build_tools/obj/build/rust/tests/test_rlib_crate/test_rlib_crate_associated_bin_test_rlib_crate_associated_bin_vunknown_build_script.ninja': The system cannot find the path specified. So my python 3.10 install didn't have a "button at end" to set the max_path/LongPathsEnabled registry entry. So I did it myself adding it to the registry through power shell. Guess what you have to do when you add a registry entry for LongPathsEnabled? You need to reboot for that one. A lot of registry entries don't require it these days, but that one does. Might want to add that under "Other build requirements" in the readme file. So I think the last issue might be the Msys2 setup. How can we keep "pacman -S quilt python3 vim tar dos2unix" from doing it's own thing. I know many a packager but pacman I do not. It insists on 3.12 no matter what I do. We might need a note on that in the readme now too. |
|
I was successful in the most simplified build and packaged as well. So it was for sure the max_path that was getting in the way. Those errors could really use some work. I think the pacman install worked okay on the patching even though it's at python 3.12 and throws that error. Now as I add cutomizations to first run, initial_preferences, icons, constants, and OWNERS, is there a command to run a quick recompile. I tried some various ninja invocations but those result in error. Maybe we need to create a wiki article on customizations. |
|
|
Wouldn't "third_party\ninja\ninja.exe -C out/Default chrome chromedriver mini_installer" from the src be quicker and more granular in the build. Or does it need to rerun everything else for some reason. build.py --ci seems a very long route since everything in src is already prebuilt from the first run. Just wondering. |
|
I give up. Can find no way of rebuilding with modifications after first build. If I wanted a Chromium stock I would just download a binary and be done with it. Too many headaches on Windows I guess. The build tools just don't act right now in 2024 it seems. The following was after a perfect stock build. Does the same whether I adjust src or not; just will not rebuild ever. I hate Windows for things like this, don't know how Microsoft ever made it. C:\ungoogled-chromium-windows>python3 build.py --ci C:\ungoogled-chromium-windows\build\src>set DEPOT_TOOLS_WIN_TOOLCHAIN=0 C:\ungoogled-chromium-windows\build\src>"third_party\ninja\ninja.exe" "-C" "out\Default" "chrome" "chromedriver" "mini_installer" C:\ungoogled-chromium-windows\build\src>exit |
Has anybody successfully build this from scratch for the last few years? I see a lot of deprecation including Rust which is quite old. Just wondering if I am chasing a dead horse or not. Would be nice to know the success rate, and if anybody has any mods to make it finish up it's build without error, (delete source takes forever, try again).
Thanks,
BigWil
The text was updated successfully, but these errors were encountered: