Building Android Chrome - rbe-chromium-untrusted

[Burner]

Is it possible to build Android Chrome (or Chrome) without and reclient/RBE?  I followed the instructions here:  Chromium Docs - Checking out and building Chromium for Android

When I run autoninja -C out/Default chrome_public_apk I get

You can't use rbe-chrome-untrusted on non-corp machine. Plase use rbe-chromium-untrusted and no...@google.com account instead to build chromium.

When I run gn ls out/Default I get,

reclient config file '..src/buildtools/reclient_cfgs/chromium-browser -clang/wrapper_linux.cfg' doesn't exist

...

To build with gn arg 'use_remoteexec=true' as a non-googler set the appropriate 'rclient_cfg_dir' value in args.gn, and refers to here: Chromium Docs - Checking out and building Chromium on Linux

As a separate issue, the materials for building Android should be updated to say at least 115GB of free disk space. I set my Ubuntu VM at 120GB (OS used 8GB) and I ran out of space.

[Haiyang Pan]

For the reclient setup, can you follow https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md#use-reclient and update mentioned files accordingly?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/bbe5930f-84a0-4c5c-8ff4-aea87baad2ebn%40chromium.org.

--

Best,

Haiyang

[Fumitoshi Ukai (鵜飼文敏)]

to build without reclient/RBE, drop `use_remoteexec=true` (and `use_recleint=true`) from args.gn

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CA%2B1sxgb0_3T-jC4cxVHtCH8NTXFOu0z_PtFvTL-f6WsewNssTg%40mail.gmail.com.

[Fumitoshi Ukai (鵜飼文敏)]

On Sat, Apr 19, 2025 at 6:32 AM Burner <ralanb...@gmail.com> wrote:

Thanks for the suggestion. This worked to start the build, but it crashed about mid-way through. There error message is indecipherable to me.  The tail end of it is:

Guess oom-killed. i.e. you don't have enough resources (esp. memory) to build.

`android_static_analysis="off"` in args.gn  may help?

 

Alan

[Burner]

Thanks for the suggestion. This worked to start the build, but it crashed about mid-way through. There error message is indecipherable to me.  The tail end of it is:

Alan

On Monday, April 7, 2025 at 5:36:10 PM UTC-7 Fumitoshi Ukai (鵜飼文敏) wrote:

[Burner]

I haven't set my build environment up to use rbe  since it was not clear to me whether this required a chromium.org account.  

From the directons,

For contributors who have tryjob access , please ask a Googler to email acco...@chromium.org on your behalf to access RBE backend paid by Google. Note that reclient for external contributors is a best-effort process. We do not guarantee when you will be invited. Reach out to reclien...@chromium.org if you have any questions about reclient usage.

To get started, you need access to an REAPI-compatible backend. The following instructions assume that you received an invitation from Google to use Chromium's RBE service and were granted access to it. However, you are welcome to use any of the other compatible backends, in which case you will have to adapt the following instructions regarding the authentication method, instance name, etc. to work with your backend.

I reached out to reclien...@chromium.org and got a bounce back message: We're writing to let you know that the group you tried to contact (reclient-users) may not exist, or you may not have permission to post messages to the group.

As a temporary workaround is there a pre-built version of Android Chrome that is built for debugging?

Thanks,

Alan