Skip to content

Build definitions for making prebuilds of Chromium modules

License

Notifications You must be signed in to change notification settings

holepunchto/chromium-prebuilds

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

41 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

chromium-prebuilds

Build definitions for making prebuilds of Chromium modules.

Setup

Like Chromium itself, this repository is not intended for checkout using git clone. Instead, start by installing depot_tools which is a toolset used for fetching and managing the Chromium source repositories. Next, create a new directory that will contain the Chromium sources and change into it:

mkdir chromium && cd chromium

Then, create a .gclient configuration file that will fetch this repository and its dependencies:

gclient config --name src/prebuilds [--cache-dir <path>] --unmanaged git@github.com:holepunchto/chromium-prebuilds.git

The --cache-dir argument, if provided, should point to a path, such as ~/.git_cache, that will be used for caching all cloned git repositories. When finished, fetch the repository and its dependencies:

gclient sync

This will take a while depending on the speed of your connection. When completed, create a link to the fetched build tools to mark the root of the build tree:

# POSIX
ln -s src/buildtools buildtools

# Windows
mklink /j buildtools src\buildtools

Patching

The build definitions rely on a few patches that must be manually applied after each gclient sync. The patches can be applied using git:

git apply --directory src src/prebuilds/patches/*.patch

Make sure to revert the patches before doing another gclient sync as it requires a clean working tree:

git apply --reverse --directory src src/prebuilds/patches/*.patch

License

Apache-2.0

About

Build definitions for making prebuilds of Chromium modules

Resources

License

Stars

Watchers

Forks

Languages