This page describes how to use the Chromium OS SDK as standalone package, without anything on top.
For the most part, you should know what you're doing to go this way.
NOTE: It is not possible to switch toolchains or install new ones, as well as generally update the system in any way. If you want a newer version, delete all and start over.
The latest version of SDK can be located in chromiumos-overlay.git repository, in sdk_version.conf
The individual SDK tarballs can be found in the Google Storage mirror: http://commondatastorage.googleapis.com/chromiumos-sdk/
In order to download the latest SDK automatically, you can execute:
eval $(curl -s https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/chromeos/binhost/host/sdk_version.conf?format=TEXT | base64 -d | grep '^SDK_LATEST_VERSION=') wget "https://commondatastorage.googleapis.com/chromiumos-sdk/cros-sdk-${SDK_LATEST_VERSION}.tar.xz"
Unzip the SDK to a folder of your choice, for example “./sdk”:
mkdir sdk cd sdk tar xvf ../cros-sdk-${SDK_LATEST_VERSION}.tar.xz
Enter by using chroot:
sudo chroot . /bin/bash
These are mostly optional and depend on what do you want to do inside the chroot. For merely running gcc, you should need neither.
sudo cp /etc/resolv.conf /etc/hosts sdk/etc/
This usually needs to be done only once unless your host's network is dynamic.mount -t proc none /proc; sudo mount -t sysfs none /sys
NOTE: If you set up these mounts, and then rm -rf sdk, you're up for a nasty surprisesudo mount -o bind /dev sdk/dev
NOTE: Same as above.Remember to clean up the chroot (especially) from mounts after you stop using it.