Update Linux build instructions for Docker
Adds a short section to the Linux build instructions on getting Chromium compilation to work in a Docker container. This is not a common setup, but this should give anyone that does need to use it a good starting place. Bug: 1377520 Change-Id: I64b78d2578012faab5070582a28d0dc9c6f41c44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4018936 Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by: Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/main@{#1069443}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
21063c77fe
commit
cadbcd2632
@ -21,6 +21,21 @@ Are you a Google employee? See
|
|||||||
Most development is done on Ubuntu (currently 18.04, Bionic Beaver). There are
|
Most development is done on Ubuntu (currently 18.04, Bionic Beaver). There are
|
||||||
some instructions for other distros below, but they are mostly unsupported.
|
some instructions for other distros below, but they are mostly unsupported.
|
||||||
|
|
||||||
|
### Docker requirements
|
||||||
|
|
||||||
|
While it is not a common setup, Chromium compilation should work from within a
|
||||||
|
Docker container. If you choose to compile from within a container for whatever
|
||||||
|
reason, you will need to make sure that the following tools are available:
|
||||||
|
|
||||||
|
* `curl`
|
||||||
|
* `git`
|
||||||
|
* `lsb_release`
|
||||||
|
* `python3`
|
||||||
|
* `sudo`
|
||||||
|
|
||||||
|
There may be additional Docker-specific issues during compilation. See
|
||||||
|
[this bug](https://crbug.com/1377520) for additional details on this.
|
||||||
|
|
||||||
## Install `depot_tools`
|
## Install `depot_tools`
|
||||||
|
|
||||||
Clone the `depot_tools` repository:
|
Clone the `depot_tools` repository:
|
||||||
|
Reference in New Issue
Block a user