On Mon, Aug 24, 2009 at 1:53 PM, Scott Hess<sh...@chromium.org> wrote: > Would it be possible/reasonable to use distcc plus a farm of > cross-compiler machines to let you do faster self-hosted builds? It's > not the "right" solution, but in the past I've found it to sometimes > be an easier path to take in the short term while you're working on > fixing all the little problems. > > -scott
Interesting take, it might work. Like Dean mentions, we're talking about 512 MB boards (or even 256 MB), which in practice only means about 400 MB accessible to the OS. I don't know how gold performs on ARM. Antoine > > > On Fri, Aug 21, 2009 at 12:54 PM, Antoine Labour<pi...@chromium.org> wrote: >> >> There's growing interest from several parties in getting Chrome to >> cross-compile onto linux/ARM. Let's make sure everyone is on the same >> page so that we don't duplicate efforts. >> I understand that Joel Stanley, Dean McNamee and Lei Zhang have >> already been doing a lot of work towards that. There's a wiki page >> there: http://code.google.com/p/chromium/wiki/LinuxChromiumArm >> >> I've identified a few missing pieces to get a full version of chrome - >> there may be others. They are mostly build infrastructure issues: >> - v8 snapshotting needs to be disabled currently, we'd like to enable >> it. That means executing mksnapshot as a target executable, either >> through qemu or directly on device, i.e. the infrastructure to run a >> target program. >> - Gyp uses pkg-config to find includes/lib dependencies, i.e. it's >> going to look at the host for them. If your target distribution >> matches your host maybe you're fine, but it may not work at all, so >> it'd would be good to extract that and get a way to specify the >> dependencies explicitly. >> - The chrome os build relies on the protobuf compiler. The current >> build system builds it as a target executable, so we either need to >> run in qemu / on device it as above, or change the build system to >> understand target vs host executables. >> >> I wanted to double check if anyone was working on any of that, or if >> anyone has good ideas about how to achieve each of them. Please speak >> up ! >> >> Antoine >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
