Abuild - Revision history

Uwe: abuild --help

2010-09-24T20:01:03Z

abuild --help

Uwe: Logs are in a top-level coreboot-builds dir.

2010-09-24T17:52:24Z

Logs are in a top-level coreboot-builds dir.

Uwe: Only invokation from top-level dir is supported in recent abuild versions.

2010-09-24T17:48:25Z

Only invokation from top-level dir is supported in recent abuild versions.

Uwe at 17:42, 24 September 2010

2010-09-24T17:42:20Z

Stepan at 12:59, 5 February 2010

2010-02-05T12:59:38Z

Uwe at 15:59, 23 April 2009

2009-04-23T15:59:00Z

Hailfinger: Created page with 'abuild is a great tool to check whether your tree compiles for one or all targets. If you invoke abuild with no parameters, it will build all boards automatically. The resulting...'

2009-04-22T23:56:17Z

Created page with 'abuild is a great tool to check whether your tree compiles for one or all targets. If you invoke abuild with no parameters, it will build all boards automatically. The resulting...'

New page

abuild is a great tool to check whether your tree compiles for one or all targets.

If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the coreboot-builds/ subdirectory of the current directory.

To build the thomson ip1000 target, run
cd util/abuild; abuild -t thomson/ip1000
The build log will be in util/abuild/coreboot-builds/thomson_ip1000/make.log

As an alternative, you can build in the top level directory.
util/abuild/abuild -t thomson/ip1000 $PWD

You can also specify a payload directory with -p

mkdir payloads
cp /somewhere/filo.elf payloads
then add a file payloads/payload.sh which prints the name of the payload
to use (and takes the mainboard as a parameter)
such as
echo "`dirname $0`/build/filo.elf"

then you can build a fully working image with payload by specifying:

util/abuild/abuild -t thomson/ip1000 -p ./payloads $PWD

Specify -c max or -c 2 if you have an SMP system, to speed compilation up.

@@ Line 1: / Line 1: @@
 '''abuild''' is a great tool to check whether your coreboot tree compiles for one or all targets.
 If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''coreboot-builds/''' directory.
@@ Line 22: / Line 24: @@
   $ '''util/abuild/abuild -t thomson/ip1000 -p ./payloads'''
-You can specify '''-c max''' (e.g. '''-c 2''') if you have an SMP system, to speed up compilation.
+== Options ==

@@ Line 1: / Line 1: @@
 '''abuild''' is a great tool to check whether your coreboot tree compiles for one or all targets.
-If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''util/abuild/coreboot-builds/''' directory.
+If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''coreboot-builds/''' directory.
 For example, to build the Thomson IP1000 target, run:
@@ Line 7: / Line 7: @@
   $ '''util/abuild/abuild -t thomson/ip1000'''
-The build log will be in '''util/abuild/coreboot-builds/thomson_ip1000/make.log'''.
+The build log will be in '''coreboot-builds/thomson_ip1000/make.log'''.
 You can also specify a payload directory with '''-p''':

@@ Line 1: / Line 1: @@
 '''abuild''' is a great tool to check whether your coreboot tree compiles for one or all targets.
-If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''coreboot-builds/''' subdirectory of the current directory.
+If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''util/abuild/coreboot-builds/''' directory.
 For example, to build the Thomson IP1000 target, run:
-  $ '''cd util/abuild; ./abuild -t thomson/ip1000'''
+  $ '''util/abuild/abuild -t thomson/ip1000'''
 The build log will be in '''util/abuild/coreboot-builds/thomson_ip1000/make.log'''.
 You can also specify a payload directory with '''-p''':
@@ Line 24: / Line 20: @@
 Then you can build a fully working image with payload by specifying:
-  $ '''util/abuild/abuild -t thomson/ip1000 -p ./payloads $PWD'''
+  $ '''util/abuild/abuild -t thomson/ip1000 -p ./payloads'''
 You can specify '''-c max''' (e.g. '''-c 2''') if you have an SMP system, to speed up compilation.

@@ Line 3: / Line 3: @@
 If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''coreboot-builds/''' subdirectory of the current directory.
-To build the thomson ip1000 target, run
+For example, to build the Thomson IP1000 target, run:
-  cd util/abuild; abuild -t thomson/ip1000
+  $ '''cd util/abuild; ./abuild -t thomson/ip1000'''
 The build log will be in '''util/abuild/coreboot-builds/thomson_ip1000/make.log'''.
-As an alternative, you can build in the top level directory.
+As an alternative, you can build in the top level directory:
-  util/abuild/abuild -t thomson/ip1000 $PWD
+  $ '''util/abuild/abuild -t thomson/ip1000 $PWD'''
 You can also specify a payload directory with '''-p''':
-  mkdir payloads
+  $ '''mkdir payloads'''
-  cp /somewhere/filo.elf payloads
+  $ '''cp /somewhere/filo.elf payloads'''
-Then add a file '''payloads/payload.sh''' which prints the name of the payload to use (and takes the mainboard as a parameter) such as
+Then add a file '''payloads/payload.sh''' which prints the name of the payload to use (and takes the mainboard as a parameter) such as:
-  echo "`dirname $0`/build/filo.elf"
+  $ '''echo "`dirname $0`/build/filo.elf"'''
 Then you can build a fully working image with payload by specifying:
-  util/abuild/abuild -t thomson/ip1000 -p ./payloads $PWD
+  $ '''util/abuild/abuild -t thomson/ip1000 -p ./payloads $PWD'''
-Specify '''-c max''' or '''-c 2''' if you have an SMP system, to speed up compilation.
+You can specify '''-c max''' (e.g. '''-c 2''') if you have an SMP system, to speed up compilation.

← Older revision		Revision as of 12:59, 5 February 2010
Line 1:		Line 1:
−	'''abuild''' is a great tool to check whether your coreboot ~~(v2)~~ tree compiles for one or all targets.	+	'''abuild''' is a great tool to check whether your coreboot tree compiles for one or all targets.

	If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''coreboot-builds/''' subdirectory of the current directory.		If you invoke abuild with no parameters, it will build all boards automatically. The resulting images and logs will end up in the '''coreboot-builds/''' subdirectory of the current directory.