From a7848665f1ca6df2a2d3e1073cf7a925a47b588b Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Mon, 3 Jun 2019 12:26:29 -0400 Subject: adjust approach to header links --- static/build.html | 75 ++++++++++++++++++++----------------------------------- 1 file changed, 27 insertions(+), 48 deletions(-) (limited to 'static/build.html') diff --git a/static/build.html b/static/build.html index 593ff1ad..cc3656ec 100644 --- a/static/build.html +++ b/static/build.html @@ -20,7 +20,7 @@ - + @@ -38,10 +38,11 @@
-

Build

+

+ Build +

- Build dependencies - + Build dependencies

- Downloading source code - + Downloading source code

Since this is syncing the sources for the entire operating system and application @@ -65,8 +65,7 @@ work properly than dealing with a moving target.

- Development branch - + Development branch

The pie branch is currently used for all supported devices:

@@ -81,8 +80,7 @@ repo sync -j32 succeed.

- Stable release - + Stable release

Pick a specific build for a device from the releases page @@ -118,8 +116,7 @@ cd ../.. verify by default.

- Updating and switching branches or tags - + Updating and switching branches or tags

To update the source tree, run the repo init command again to select @@ -131,8 +128,7 @@ cd ../.. GrapheneOS only provides a stable history via tags.

- Browser and WebView - + Browser and WebView

Before building GrapheneOS, you need to build Chromium for the WebView and @@ -184,8 +180,7 @@ git am ../chromium_patches/*.patch frameworks/base/core/res/res/xml/config_webview_packages.

- Kernel - + Kernel

The kernel needs to be built in advance, since it uses a separate build system.

@@ -212,8 +207,7 @@ git submodule update --init generated per the instructions below before building the kernel.

- Setting up the OS build environment - + Setting up the OS build environment

The build has to be done from bash as envsetup.sh is not compatible with other @@ -233,8 +227,7 @@ git submodule update --init make additional performance sacrifices to improve debugging.

- Reproducible builds - + Reproducible builds

To reproduce a past build, you need to export BUILD_DATETIME and @@ -251,8 +244,7 @@ git submodule update --init signatures.

- Extracting vendor files for Pixel devices - + Extracting vendor files for Pixel devices

This section does not apply to devices where no extra vendor files are required (HiKey, HiKey 960, emulator, generic targets).

@@ -276,8 +268,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/ passed with --timestamp (seconds since Epoch).

- Building - + Building

Incremental builds (i.e. starting from the old build) usually work for development @@ -295,8 +286,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/ 

make target-files-package -j20

- Faster builds for development use only - + Faster builds for development use only

The normal production build process involves building a target files package to be @@ -318,8 +308,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/ keys.

- Generating release signing keys - + Generating release signing keys

Keys need to be generated for resigning completed builds from the publicly @@ -343,8 +332,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/ done before building the kernel

- Android Verified Boot 1.0 - + Android Verified Boot 1.0

To generate keys for marlin (you should use unique keys per device variant):

@@ -371,8 +359,7 @@ out/host/linux-x86/bin/generate_verity_key -convert keys/marlin/verity.x509.pem no separate sailfish kernel.

- Android Verified Boot 2.0 (AVB) - + Android Verified Boot 2.0 (AVB)

To generate keys for crosshatch (you should use unique keys per device @@ -392,8 +379,7 @@ cd ../.. rather to set the public key used by the device to enforce verified boot.

- Generating signed factory images and full update packages - + Generating signed factory images and full update packages

Build the tool needed to generate A/B updates:

@@ -413,8 +399,7 @@ cd ../.. zip.

- Prebuilt code - + Prebuilt code

Like the Android Open Source Project, GrapheneOS contains some code that's built @@ -422,25 +407,21 @@ cd ../.. gradually expanded to cover building all of it.

- Prebuilt apps - + Prebuilt apps

The Auditor app is simply built from the latest upstream tag and bundled as an apk into external/ repositories. There are no modifications to it for GrapheneOS.

- Testing - + Testing

- Compatibility Test Suite - + Compatibility Test Suite

- Download - + Download

Testing with the Compatibility Test Suite (CTS) can be done by either building the @@ -453,8 +434,7 @@ cd ../.. CTS Media Files also needs to be downloaded from that section.

- Setup - + Setup

You'll need a device attached to your computer with ADB enabled along with the Android SDK installed. The build-tools and platform-tools packages need to be @@ -495,8 +475,7 @@ export PATH="$PATH:$HOME/sdk/tools:$HOME/sdk/tools/bin:$HOME/sdk/platform-tools:

- Run modules - + Run modules

Run the test harness:

-- cgit v1.3.1