|Upcoming build system changes||Ryan Cairns||2/5/10 2:57 PM|
As we’ve been growing and working with more partners, the need to support board specific builds and improve our tools has become more urgent. In order to get there more quickly we’ve been investigating several different build tools. We found that the Portage build tools suit our needs well and we will be transitioning 100% within the next week.
To date, we’ve completed the following
We still have a lot more work to do before we’ll be satisfied with where we’re at, but over the next week our goal will be to get everything working perfectly with the new build system.
|Re: [cros-dev] Upcoming build system changes||ack||2/8/10 2:56 PM|
The Portage-based build instructions don't mention anything about building the chromium browser or downloading a chromium binary - is this subsumed into one of the ./new_... build scripts?
(A portage build I did yesterday - build on EC2 64-bit karmic instance, image/... copied to 32-bit laptop for non-chroot ./image_to_usb.sh - behaved interestingly - it booted into a familiar blue chromium os screen but without any obvious means of login.)
|Re: [cros-dev] Upcoming build system changes||Matt Richards||2/8/10 4:06 PM|
Confirmed on IRC today, the current revsion only downloads a binary of
the browser from the buildbot. Plan is to have it compile the code
Question I have though, do the vmware/virtualbox scripts still
|Re: [cros-dev] â€‹Upcoming build system changes||Nasser Grainawi||2/8/10 7:46 PM|
Looks like so long as you give it a --from=<path to rootfs.image dir> it
The new build system sticks those images into dirs under src/build/images/*
If you run ./new_build_image.sh, you'll see it print this at the end: