From 81e66c3172a5c960b173df719f26ebfec183e3fc Mon Sep 17 00:00:00 2001
From: Francis Rowe
Date: Wed, 31 Dec 2014 01:39:41 +0000
Subject: build-release: include statically (cross) compiled cbfstool
---
build-release | 7 +++++++
docs/git/index.html | 7 +++++++
2 files changed, 14 insertions(+)
diff --git a/build-release b/build-release
index 15c51223..a958c015 100755
--- a/build-release
+++ b/build-release
@@ -203,6 +203,13 @@ if [ "$arch" = "x86_64" ]
mv rmodtool ../../../libreboot_bin/cbfstool/i686/
fi
+# cross-compile for ARM
+make clean
+make SHARED=0 CC='arm-linux-gnueabi-gcc -static'
+mkdir ../../../libreboot_bin/cbfstool/armv7l
+mv cbfstool ../../../libreboot_bin/cbfstool/armv7l/
+mv rmodtool ../../../libreboot_bin/cbfstool/armv7l/
+
cd ../
rm -rf cbfstool
mv cbfstool_ cbfstool
diff --git a/docs/git/index.html b/docs/git/index.html
index 53ffd1db..01f225b2 100644
--- a/docs/git/index.html
+++ b/docs/git/index.html
@@ -502,6 +502,13 @@
and bucts will be included only as 64-bit statically linked binaries. To include a statically linked flashrom and bucts for i686, you
will need to build them on a chroot, a virtual machine or a real 32-bit system. You can find the build dependencies for these packages listed in deps-*
+
+
+ armv7l binaries (tested on a BeagleBone Black) are also included in libreboot_bin, for:
+
+
If you are building 32-bit binaries on a live system or chroot (for flashrom/bucts), you can use the following to statically link them:
--
cgit v1.2.3-70-g09d2