From 4b0752e1c264c4ba2a354507ca97bb2e039dda1a Mon Sep 17 00:00:00 2001 From: "4 of 7 (Leah Rowe) info@minifree.org" Date: Sat, 21 Jan 2017 18:14:33 +0000 Subject: re-add old build system (for x86 boards/utils) Everything will be migrated over to the new build system after release. --- docs/git/index.html | 62 ++++++++++++++++++++++++++--------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) (limited to 'docs/git') diff --git a/docs/git/index.html b/docs/git/index.html index 2b85000a..4ccb7b27 100644 --- a/docs/git/index.html +++ b/docs/git/index.html @@ -45,14 +45,14 @@

For Debian Stretch (may also work on Debian Jessie), you can run the following command:
- $ sudo ./build dependencies debian + $ sudo ./oldbuild dependencies debian
(this will also work in Devuan)

For Parabola, you can run the following command:
- $ sudo ./build dependencies parabola
+ $ sudo ./oldbuild dependencies parabola
or:
- # ./build dependencies parabola + # ./oldbuild dependencies parabola

@@ -176,12 +176,12 @@

To build bucts, do this in the main directory:
- $ ./build module bucts + $ ./oldbuild module bucts

To statically compile it, do this:
- $ ./build module bucts static + $ ./oldbuild module bucts static

@@ -217,12 +217,12 @@

To build it, do the following in the main directory:
- $ ./build module flashrom + $ ./oldbuild module flashrom

To statically compile it, do the following in the main directory:
- $ ./build module flashrom static + $ ./oldbuild module flashrom static

@@ -281,36 +281,36 @@

Build all of the components used in libreboot:
- $ ./build module all + $ ./oldbuild module all

- You can also build each modules separately, using ./build module modulename. + You can also build each modules separately, using ./oldbuild module modulename. To see the possible values for modulename, use:
- $ ./build module list + $ ./oldbuild module list

After that, build the ROM images (for all boards):
- $ ./build roms withgrub
+ $ ./oldbuild roms withgrub
Alternatively, you can build for a specific board or set of boards. For example:
- $ ./build roms withgrub x60
- $ ./build roms withgrub x200_8mb
- $ ./build roms withgrub x60 x200_8mb
+ $ ./oldbuild roms withgrub x60
+ $ ./oldbuild roms withgrub x200_8mb
+ $ ./oldbuild roms withgrub x60 x200_8mb
The list of board options can be found by looking at the directory names in resources/libreboot/config/grub/.

For those boards which use the depcharge payload, you must use: - $ ./build roms withdepthcharge
+ $ ./oldbuild roms withdepthcharge
You can also build for a specific board or set of boards. For example:
- $ ./build roms withdepthcharge veyron_speedy + $ ./oldbuild roms withdepthcharge veyron_speedy

To clean (reverse) everything, do the following:
- $ ./build clean all + $ ./oldbuild clean all

@@ -334,7 +334,7 @@

- The archives will appear under release/${version}/; + The archives will appear under release/oldbuildsystem/${version}/; ${version} will either be set using git describe or, if a version file already exists (_src release archive), then it will simply re-use that. @@ -342,34 +342,34 @@

Tag the current commit, and that version will appear in both the ${version} - string on the directory under release/, and in the file names of the + string on the directory under release/oldbuildsystem/, and in the file names of the archives. Otherwise, whatever git uses for git describe --tags HEAD will be used.

Utilities (static executables):
- $ ./build release util + $ ./oldbuild release util

Archive containing flashrom and bucts source code:
- $ ./build release tobuild + $ ./oldbuild release tobuild

Documentation archive (does not work on _src release archive, only git):
- $ ./build release docs + $ ./oldbuild release docs

ROM image archives:
- $ ./build release roms + $ ./oldbuild release roms

Source code archive:
- $ ./build release src + $ ./oldbuild release src

SHA512 sums of all other release archives that have been generated:
- $ ./build release sha512sums + $ ./oldbuild release sha512sums

@@ -405,8 +405,8 @@

If you are building binaries on a live system or chroot (for flashrom/bucts), you can use the following to statically link them:
- $ ./build module flashrom static
- $ ./build module bucts static + $ ./oldbuild module flashrom static
+ $ ./oldbuild module bucts static

@@ -417,17 +417,17 @@

The command that you used for generating the release archives will also run the following command:
- $ ./build release tobuild
- The archive tobuild.tar.xz will have been created under release/, containing bucts, flashrom and all other required + $ ./oldbuild release tobuild
+ The archive tobuild.tar.xz will have been created under release/oldbuildsystem/, containing bucts, flashrom and all other required resources for building them.

- You'll find that the files libreboot_util.tar.xz and libreboot_src.tar.xz have been created, under release/. + You'll find that the files libreboot_util.tar.xz and libreboot_src.tar.xz have been created, under release/oldbuildsystem/.

- The ROM images will be stored in separate archives for each system, under release/rom/. + The ROM images will be stored in separate archives for each system, under release/oldbuildsystem/rom/.

-- cgit v1.2.3-70-g09d2