[Chromebooks] fattire:
From what I remember, the build system would do whatever key signing was necessary.... although I do now remember you're right there was some manual step when I was building the kernel, but I can't remember if that's because of MY changes or that was just part of the build process.

I I just dug out the old VM (Xubuntu) I was using to build and, well, let's just say I'll be doing a LOT of ubuntu updates before I can even realistically look at this. I do kinda recall setting up the environment was a huge pain so I'm going to see if I can just update the 5 year old source, target the pro and just build the kernel image and see what pops out the other end. At least I won't have to deal with the cross compiler, though I think it should hopefully take care of that itself.

Interesting to see that those crouton projects have emerged (no pun intended) so I'll check them out too while ubuntu updates itself

Thanks for the github links.. I'm going to go read that wiki.

Update: Looked at it-- funny they just stripped out the chromeos-specific parts they needed rather than emerge everything which is smart. My only question is now that Android is involved, there's that script I linked to earlier that seems to say "if you want Android support you'll need these bits too"-- wonder if the same config scripts apply, and if there are any other device tree considerations as well...

I may play a bit and see how smoothly it goes.. Unfortunately I don't have unlimited time either :/

Also, please do let me know if you put the scripts on github and I can send you pull requests if I come up with anything.

Update: Finally updated like 3 major versions of ubuntu... the "depot_tools" repo had its last commit in 2013, so I updated that. Wow, this is so much clearer than previous docs... it looks like something called gclient is used now, which I configured with:

gclient config --spec 'solutions = [

{

"url": "https://chromium.googlesource.com/chromium/src.git",

"managed": False,

"name": "src",

"deps_file": ".DEPS.git",

"custom_deps": {},

},

]

'

that let me do gclient sync --nohooks --no-history ...which i think is updating the ancient source. I probably should have just started over, but anyway... we'll see what happens.

Update again: After updating with this new gclinet tool, it appears that the old repo sync method is still required as described here. That hasn't changed after all, so now I'm going to go through this old method, which will probably completely overwhelm my storage as it's downloading with history.. but anyway, in case anyone is trying this-- looks like the whole chroot/repo sync thing may still be how it's done... the /src directory described above may only be for building just the browser, not the whole OS...

...and here it is. I will have zero room to actually build anything tho, but hey.

* [new branch] release-R58-9334.B-caroline-chromeos-3.18 -> cros/release-R58-9334.B-caroline-chromeos-3.18

Note to self: use cros_sdk --enter to actually get in the chroot. Then:

~/trunk/src/scripts $ ./setup_board --board=caroline

to set up the build for caroline. Then to build:

./build_packages --board=caroline --nowithdebug

Useful links:

* Building ChromiumOS

* [URL="http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/portage-build-faq"]eBuild FAQ

[/URL]