Maru hooks into the AOSP build system for the majority of the build process.
# Build the desktop image
Tip: You can just download the latest prebuilt image from here (opens new window) if you don't want to build the desktop image yourself. It can take up to 30 minutes for the build to finish.
The one exception to the AOSP build system is the build process for the desktop image.
$ cd vendor/maruos/blueprints $ ./build.sh -b debian -n stretch-container -- -r stretch -a arm64 --minimal
Tip: You may need to run the last
./build.sh script with sudo if you are using docker.
After half-an-hour or so, you should have the final desktop image under
out/. It will look like
Copy the final image over to
vendor/maruos/prebuilts, where the AOSP build system will pick it up in the next step:
$ cp out/maru-* ../prebuilts/desktop-rootfs.tar.gz
The desktop image will be cached under
vendor/maruos/prebuilts from here on out so you won't need to build it often. Just remember to generate a new image whenever maruos/blueprints (opens new window) has significant changes to make sure your desktop is up-to-date.
# Build the device image
# Get the device binaries
There are usually proprietary binary drivers ("blobs") you'll need to download to get some of your device hardware to properly function. These are not available as part of the AOSP project, so you will need to obtain them from friendly hardware manufacturers.
For Nexus devices, you can download the blobs straight from the Nexus Binaries page (opens new window). Make sure to select the right binaries for your device and build version!
For example, let's say you want to build Maru OS v0.6 for Nexus 5X (bullhead). v0.6 is based on android-8.1.0_r52 (OPM7.181205.001), so you would download the bullhead OPM7.181205.001 binaries (opens new window).
Tip: To find the right binary version to select, check the manifest file that you used to sync your workspace. You can find the AOSP tag that Maru OS is based on in the manifest's default.xml (opens new window). (Verify that the branch you're on is the same as the version of MaruOS you wanna build) You can correlate this to the build code listed on the Nexus Binaries page here (opens new window).
Uncompress each of the binary tars and run them (they are self-extracting scripts) from the root of your $WORKSPACE, making sure you read and agree to the license terms:
$ for f in *.tgz ; do tar xzf "$f" ; done $ for f in extract-*.sh ; do ./"$f" ; done
You will now have the blobs under
# Nexus 5x (bullhead)
For the Nexus 5X, the vendor blobs are not sufficient. The device will bootloop if you use the binary blobs as described above.
Please see the bullhead device README (opens new window) to prepare the vendor directory from a factory image.
# Configure the build system
You'll need to source some environment variables to initialize the build system. From the top of your $WORKSPACE:
$ . build/envsetup.sh
List the device build configurations with:
Then select the device you'd like to build. Any of the devices with the prefix
maru_ are supported by Maru OS. For instance, select
maru_hammerhead-userdebug for a developer build for Nexus 5 (hammerhead).
# Now build!
$ mka # performant wrapper for parallel make
Tip: This build can take a long time. Set up ccache (opens new window) to speed things up.
# Flashing Builds
Connect your device to your machine over USB, and reboot your device into the bootloader:
$ adb reboot bootloader
...and flash your build:
$ fastboot -w flashall
Tip: You may need to unlock your bootloader (opens new window) if this is the first time you are flashing custom software.
# Flashing with Docker
You will need to give your container USB access by bind mounting
$ docker run --privileged -it \ -v /dev/bus/usb:/dev/bus/usb \ -v ~/path/to/$WORKSPACE:/var/maru \ pdsouza/maruos-devbox
# Building an OTA zip
In addition to doing a standard build, you can also build an OTA zip for your device that can be flashed via a custom recovery like TWRP. These OTA zips are the standard format for distributing official Maru images.
To generate the OTA zip:
$ mka dist
After the build is complete, you will find the OTA zip in a file like
# References / Further Reading
- AOSP build docs (opens new window)