Adds instructions for using Docker to build Chromium for Android. This
change includes a guide for creating a Docker image with all needed
tools and dependencies, running the container, and building Chromium
inside it.
Previously, setting up the build environment required manual steps that
were prone to errors. The new Docker setup makes it easier and more co-
nsistent.
Change-Id: Ia0211f7e8c40c86d172c42e292c82833aa1a2a90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5870117
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1369455}
Much of our documentation on how to build Chromium/etc. says that an
"Intel" machine is needed. This has never been true. What is needed is
an x86-64 machine - it could be Intel, AMD, or a custom processor
with transistors created using very small tweezers.
This change simply replaces [64-bit] Intel with x86-64 in seven places
in our documentation.
Change-Id: If1d1ef045b4de85d8f12e1c2051c332ac2890624
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5627158
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1314189}
1. Goma has been deprecated. Goma in linux
build_instructions.md is replaced with
Reclient. Based on actual experience, some
contents in the Docker section are
appropriately adjusted to make it easier for
developers to use Docker to compile Chromium.
2. Improve readability of some contents in
vscode.md.
3. Delete some contents in vscode settings.json
that are repeated with vscode extensions.json.
Bug: None
Change-Id: I1a9cdf1102334280058b1d85b1dfeb0535d6ead4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5579555
Reviewed-by: Chase Phillips <cmp@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Ho Cheung <hocheung@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@google.com>
Cr-Commit-Position: refs/heads/main@{#1308378}
Building with reclient_cfg_dir is not possible when trying to build
older Chrome builds. Make a note about building with rbe_cfg_dir
in the docs.
Change-Id: I4096021d71cce964941683998cd3e96b90e9d08f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5570745
Reviewed-by: Junji Watanabe <jwata@google.com>
Commit-Queue: Brendon Tiszka <tiszka@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1306347}
This CL renames the following GN args/variables.
- rbe_bin_dir -> reclient_bin_dir
- rbe_cfg_dir -> reclient_cfg_dir
- rbe_cros_cc_wrapper -> reclient_cros_cc_wrapper
- rbe_*_cfg_file -> reclient_*_cfg_file
When an old GN arg is specified, it will print a warning message.
Bug: 342270134
Change-Id: I9b725c358b50b98bb6313351d1f8cef3f3fa4c9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5561845
Reviewed-by: Philipp Wollermann <philwo@google.com>
Reviewed-by: Michael Savigny <msavigny@google.com>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Junji Watanabe <jwata@google.com>
Cr-Commit-Position: refs/heads/main@{#1305494}
Adding the warning message again to just above the gclient file
contents, the first warning has been missed a few times.
Bug: 325928330
Change-Id: I67d625eb21178744542976a19cdf73bfa23aac41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5426233
Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Michael Savigny <msavigny@google.com>
Cr-Commit-Position: refs/heads/main@{#1285094}
This is a reland of https://crrev.com/1277898
Reason for reland: b/331404365 is fixed
Projects like V8/WebRTC/Pdfium/etc will also have to:
1. Change DEPS as in this CL
2. Rename instrumented_libraries to instrumented_libs as in this CL
R=thakis,dpranke
Cq-Include-Trybots: luci.chromium.try:linux_chromium_msan_rel_ng
Bug: 320564950
Change-Id: Id85151f41cdb44e95f5b6479d59ccbecf184f682
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5421930
Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1282953}
- `nih-dbus-tool` no longer exists, and is no longer needed. Remove it
from the list of packages that need to be installed.
- Run `apt upgrade` after `apt update`, because why not.
- Document several additional build dependencies:
- git so the GN invocation does not fail when trying to exec scripts
that use git
- gyp since several instrumented libraries (e.g. NSS) use gyp
- fakeroot since several instrumented libraries use fakeroot
- Make the command for mounting /dev/shm more copy-pastable.
- Add basic directions for removing chroots.
Bug: 1369167
Change-Id: I89fd7f8bc8e5ec8d621ccdd0a74f4ae1144065be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5404471
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1279818}
Add docker file, docker installation procedures as per requested by Brian Sheedy in GSoC Mailing List. It installs Ubuntu 22.04, build instructions and persists data on drive.
Change-Id: Id1048d015a3c2d049617d922e94253815a468b10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5380520
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1279178}
Projects like V8/WebRTC/Pdfium/etc will also have to:
1. Change DEPS as in this CL
2. Rename instrumented_libraries to instrumented_libs as in this CL
Cq-Include-Trybots: luci.chromium.try:linux_chromium_msan_rel_ng
Bug: 320564950
Change-Id: I802bce32cc37d0ec9c0081cf08a4f8179293693d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5368675
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@google.com>
Cr-Commit-Position: refs/heads/main@{#1277898}
The link for setting up reclient for googlers was actually pointing to the section of
the docs about using reclient, not setting it up. This has led to some
users missing critical setup steps.
Bug: b/308577099
Change-Id: Ic71794db3441a4af8d919deacc4c3f3e7ee37a5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4993130
Reviewed-by: Michael Ershov <miersh@google.com>
Commit-Queue: Michael Savigny <msavigny@google.com>
Cr-Commit-Position: refs/heads/main@{#1217553}
Add support for interactively debugging WPTs with upstream's `wpt run`.
`run_wpt_tests.py --verbose` ensures browser logs are dumped to stdout
so that `debug_renderer` can find the PID to attach to.
Bug: 1440021
Test: ./debug_renderer ./run_wpt_tests.py -t Default
Test: external/wpt/badging/badge-success.https.html
Change-Id: I58323aea67f6232bc28b198b8f18d3d7bb7d8a7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4893148
Reviewed-by: Weizhong Xia <weizhong@google.com>
Commit-Queue: Jonathan Lee <jonathanjlee@google.com>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1201810}
We had not updated the docs in a while so there were references
to the Python3 migration and Python3.6 still present in some
places.
This CL updates the docs to refer to the current Python version
(3.8) and removes documentation for the Python3 migration, which
is no longer necessary.
Change-Id: Id59d10d90dbd8ceff0ec8203be5e4dfbdc58c4b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4824013
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@google.com>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1190394}
Currently, the vast majority of chromium builds run on jammy. And
after https://crrev.com/c/4652993, any new builder will automatically
be running on jammy.
So jammy is now the official default for infra jobs. This updates
the docs to mention that, and clarifies them a little since the
statement about "most development" might apply to more than just CI
builds, and we can't be as confident about the OS breakdown outside
of our infra.
Bug: 1412588
Change-Id: I751abf251db9758c0b6c12733a2e06f7a5e3e5c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4654783
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1163837}
- Fix the broken link to gdbinit.md & lldbinit.md on linux/debugging.md.
- Additionally, replace the absolute link to gdbinit.md with a relative
link to maintain notation consistency with the other links in this
doc.
Bug: n/a
Change-Id: Idc275f63de05264b66d0fbe022f26dc0e0b63599
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4573957
Auto-Submit: Taiyo Mizuhashi <taiyo@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1150998}
