New issue
Advanced search Search tips

Issue 720333 link

Starred by 4 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Include arm and arm64 builds of GN in depot_tools

Project Member Reported by kjlubick@google.com, May 10 2017

Issue description

Since we can cross compile both arm and arm64, it would be nice if those binaries were included in a checkout of depot_tools.

It's a bit of a pain to have to cross compile gn, ship it to the arm box, and then begin the process of building chromium and other projects.
 
This is so you can run GN on an ARM host? Where do we do that?

Comment 2 by kjlubick@google.com, May 11 2017

I've wanted to build Skia (which uses GN) on ARM hosts such that we can fuzz them.

Cross-compiling the fuzz instrumentation has yielded no fruit, so I've settled for on-host compiling.  I've cross compiled GN for this effect, but it would be nice if it was just included.
Actually running GN on an ARM host isn't something we really any other need for, and we don't tend to have any hosts running it, so there aren't any official builds.

We don't actually include any GN binaries in depot_tools anyway; the gn.py wrapper just points back at files pulled in via DEPS (and buildtools).
Labels: TE-NeedsTriageHelp
The issue seems to be out of TE-scope. Hence, adding TE-NeedsTriageHelp for further investigation.

Thanks...!!
Components: Build
Labels: -TE-NeedsTriageHelp
Status: Available (was: Unconfirmed)
Do we really need an ARM (32-bit) binary? We don't support building chromium on 32-bit hosts any more, and AFAIK we don't distribute 32-bit ninja binaries anywhere, either, at this point.
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 17 2017

Labels: Hotlist-Google
Project Member

Comment 8 by sheriffbot@chromium.org, Jul 17

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment