Windows packaging for ungoogled-chromium.
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.
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
.
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.
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
(replace2019
andCommunity
with your installed versions)WINDOWSSDKDIR = DRIVE:\path\to\Windows Kits\10
GYP_MSVS_VERSION = 2019
(replace 2019 with your installed version's year)
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.6 or newer (you will see a button at the end of installation to do this). See Issue #345 for other methods for other Windows versions.
-
Setup the following:
- 7-zip
- Python 3.6 - 3.9 or 3.10.2+ (for build and packaging scripts used below)
- At the end of the Python installer, click the button to lift the
MAX_PATH
length restriction. - Check that your
PATH
does not contain thepython3
wrapper shipped by Windows, as it will only promt you to install Python from the Microsoft Store and exit. See this question on stackoverflow.com
- At the end of the Python installer, click the button to lift the
- 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.
NOTE: The commands below assume the py
command was installed by Python 3 into PATH
. If this is not the case, then substitute it with python3
.
Run in cmd.exe
(as administrator):
git clone --recurse-submodules https://github.com/ungoogled-software/ungoogled-chromium-windows.git
# Replace TAG_OR_BRANCH_HERE with a tag or branch name
git checkout --recurse-submodules TAG_OR_BRANCH_HERE
py build.py
py 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 removingbuild\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 underbuild
other thanbuild\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.
- Setup MSYS2
- Run the following in a "MSYS2 MSYS" shell:
pacman -S quilt python3 vim tar
# By default, there doesn't seem to be a vi command for less, quilt edit, etc.
ln -s /usr/bin/vim /usr/bin/vi
IMPORTANT: Run the following in a "MSYS2 MSYS" shell:
- Navigate to the repo path:
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>
- Setup patches and shell to update patches
./devutils/update_patches.sh merge
source devutils/set_quilt_vars.sh
- Setup Chromium source
mkdir -p build/{src,download_cache}
./ungoogled-chromium/utils/downloads.py retrieve -i ungoogled-chromium/downloads.ini -c build/download_cache
./ungoogled-chromium/utils/downloads.py unpack -i ungoogled-chromium/downloads.ini -c build/download_cache build/src
- Go into the source tree:
cd build/src
- Use quilt to refresh patches. See ungoogled-chromium's docs/developing.md section "Updating patches" for more details
- Go back to repo root:
cd ../..
- Remove all patches introduced by ungoogled-chromium:
./devutils/update_patches.sh unmerge
- Ensure patches/series is formatted correctly, e.g. blank lines
- Sanity checking for consistency in series file:
./devutils/check_patch_files.sh
- Check for esbuild dependency changes in file
build/src/DEPS
and adaptdownloads.ini
accordingly - Use git to add changes and commit
See LICENSE