X Tutup
Skip to content

Commit ad7e5b7

Browse files
committed
Update build instructions. Add "Building old unsupported version
of Chromium" section.
1 parent ebf7844 commit ad7e5b7

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

docs/Build-instructions.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ Table of contents:
1212
* [Build using prebuilt CEF binaries and libraries](#build-using-prebuilt-cef-binaries-and-libraries)
1313
* [Build using CEF binaries from Spotify Automated Builds](#build-using-cef-binaries-from-spotify-automated-builds)
1414
* [Build upstream CEF from sources](#build-upstream-cef-from-sources)
15+
* [Building old unsupported version of Chromium](#building-old-unsupported-version-of-chromium)
1516
* [Possible errors](#possible-errors)
1617
* [Build CEF manually](#build-cef-manually)
1718
* [CEF Automated Builds (Spotify and Adobe)](#cef-automated-builds-spotify-and-adobe)
@@ -300,6 +301,7 @@ python ../tools/build.py xx.x
300301

301302
## Build upstream CEF from sources
302303

304+
303305
Building CEF from sources is a very long process that can take several
304306
hours depending on your CPU speed and the platform you're building on.
305307
To speed up the process you can pass the --fast-build flag, however
@@ -351,6 +353,26 @@ module, make installer package, install the package and run unit tests
351353
and examples. See the notes for commands for creating package installer
352354
and/or wheel package for distribution.
353355

356+
### Building old unsupported version of Chromium
357+
358+
When building an old version of Chromium you may get into issues.
359+
For example as of this writing the latest CEF Python version is
360+
v57, but current support Chromium version is v64. Now when building
361+
v57 you may encounter issues since Chromium build tools had
362+
many updates since v57. You have to checkout depot_tools from the
363+
revision when Chromium v57 was released. When running automate.py
364+
tool the depot_tools repository resides in `build_dir/depot_tools/`
365+
directory. If you didn't run automate.py then you can find repository
366+
url in automate-git.py script. For example for v57 release to checkout
367+
an old revision of depot_tools you can use this command:
368+
369+
```
370+
git checkout master@{2017-04-20}
371+
```
372+
373+
After that set `DEPOT_TOOLS_UPDATE=0` environment variable and then
374+
run automate.py tool.
375+
354376
### Possible errors
355377

356378
__Debug_GN_arm/ configuration error (Linux)__: Even though building

0 commit comments

Comments
 (0)
X Tutup