ungoogled-software/ungoogled-chromium-windows is one of the open-source repositories TopGit tracks, currently at 2.5k stars, written primarily in Python. Windows packaging for ungoogled-chromium
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Download binaries from the Contributor Binaries website.
Or install using winget install --id=eloston.ungoogled-chromium -e.
Source Code: It is recommended to use a tag via git checkout (see building instructions below). You may also use master, but it is for development and may not be stable.
Building
Google only supports Windows 10 x64 or newer. These instructions are tested on Windows 10 Pro x64.
NOTE: The default configuration will build 64-bit binaries for maximum security (TODO: Link some explanation). This can be changed to 32-bit by setting target_cpu to "x86" in flags.windows.gn or passing --x86 as an argument to build.py.
Setting up the build environment
IMPORTANT: Please setup only what is referenced below. Do NOT setup other Chromium compilation tools like depot_tools, since we have a custom build process which avoids using Google's pre-built binaries.
Setting up Visual Studio
Follow the "Visual Studio" section of the official Windows build instructions.
Make sure to read through the entire section and install/configure all the required components.
If your Visual Studio is installed in a directory other than the default, you'll need to set a few environment variables to point the toolchains to your installation path. (Copied from instructions for Electron)
vs2019_install = DRIVE:\path\to\Microsoft Visual Studio\2019\Community (replace 2019 and Community with your installed versions)
WINDOWSSDKDIR = DRIVE:\path\to\Windows Kits\10
GYP_MSVS_VERSION = 2019 (replace 2019 with your installed version's year)
Other build requirements
IMPORTANT: Currently, the MAX_PATH path length restriction (which is 260 characters by default) must be lifted in for our Python build scripts. This can be lifted in Windows 10 (v1607 or newer) with the official installer for Python 3.11 or newer (you will see a button at the end of installation to do this). See Issue #345 for other methods for older Windows versions.
Setup the following:
7-Zip
Python 3.11 or above
Can be installed using WinGet or the Microsoft Store.
If you don't plan on using the Microsoft Store version of Python:
Check "Add python.exe to PATH" before install.
At the end of the Python installer, click the button to lift the MAX_PATH length restriction.
Disable the python3.exe and python.exe aliases in Settings > Apps > Advanced app settings > App execution aliases. They will typically be referred to as "App Installer". See this question on stackoverflow.com to understand why.
Ensure that your Python directory either has a copy of Python named "python3.exe" or a symlink linking to the Python executable.
The httplib2 module at version 0.22.0. This can be installed using pip install httplib2==0.22.0.
Make sure to lift the MAX_PATH length restriction, either by clicking the button at the end of the Python installer or by following these instructions.
Git (to fetch all required ungoogled-chromium scripts)
During setup, make sure "Git from the command line and also from 3rd-party software" is selected. This is usually the recommended option.
Building
Run in Developer Command Prompt for VS (as administrator):
git clone --recurse-submodules https://github.com/ungoogled-software/ungoogled-chromium-windows.git
cd ungoogled-chromium-windows
# Replace TAG_OR_BRANCH_HERE with a tag or branch name
git checkout --recurse-submodules TAG_OR_BRANCH_HERE
python3 build.py
python3 package.py
A zip archive and an installer will be created under build.
NOTE: If the build fails, you must take additional steps before re-running the build:
If the build fails while downloading the Chromium source code (which is during build.py), it can be fixed by removing build\download_cache and re-running the build instructions.
If the build fails at any other point during build.py, it can be fixed by removing everything under build other than build\download_cache and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build.
An efficient way to delete large amounts of files is using Remove-Item PATH -Recurse -Force. Be careful however, files deleted by that command will be permanently lost.
Developer info
First-time setup
Setup MSYS2
Run the following in a "MSYS2 MSYS" shell:
pacman -S quilt python3 vim tar dos2unix
# By default, there doesn't seem to be a vi command for less, quilt edit, etc.
ln -s /usr/bin/vim /usr/bin/vi
Updating patches and pruning list
Start Developer Command Prompt for VS and MSYS2 MSYS shell and navigate to source folder
Developer Command Prompt for VS
cd c:\path\to\repo\ungoogled-chromium-windows
MSYS2 MSYS
cd /path/to/repo/ungoogled-chromium-windows
You can use Git Bash to determine the path to this repo
Or, you can find it yourself via /<drive letter>/<path with forward slashes>
Retrieve downloads
Developer Command Prompt for VS
Check the ninja version in file build/src/third_party/devtools-frontend/src/DEPS and find the closest release in the ninja GitHub to it.
Download the ninja-win.zip file.
Get the SHA-512 checksum using sha512sum in MSYS2 MSYS.
Check the Git GitHub for the latest version of Git.
Get the SHA-256 checksum for PortableGit-<version>-64-bit.7z.exe.
Check for commit hash changes of src submodule in third_party/microsoft_dxheaders (e.g. using GitHub https://github.com/chromium/chromium/tree/<version>/third_party/microsoft_dxheaders).
Replace version with the Chromium version in ungoogled-chromium/chromium_version.txt.
Check the node version changes in third_party/node/update_node_binaries (e.g. using GitHub https://github.com/chromium/chromium/tree/<version>/third_party/node/update_node_binaries).
Download the "Standalone Binary" version from the NodeJS website.
Get the SHA-512 checksum using sha512sum in MSYS2 MSYS.
Check for version changes of windows rust crate (third_party/rust/windows_x86_64_msvc/).
Download rust crate zip file.
Get the SHA-512 checksum using sha512sum in MSYS2 MSYS.
Is ungoogled-software/ungoogled-chromium-windows open source?
Yes — ungoogled-software/ungoogled-chromium-windows ships under the BSD-3-Clause license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/ungoogled-software/ungoogled-chromium-windows.
What is ungoogled-software/ungoogled-chromium-windows?
ungoogled-software/ungoogled-chromium-windows (ungoogled-software/ungoogled-chromium-windows) is a Python project on GitHub. From the project's own README: Windows packaging for ungoogled-chromium
Where do I read more about ungoogled-software/ungoogled-chromium-windows?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/ungoogled-software/ungoogled-chromium-windows is the definitive source.
Read full README in the tab above.
Still deciding about ungoogled-chromium-windows?
One click hands the question to an AI along with this page — see what it says about ungoogled-chromium-windows.
/ungoogled-chromium-windows