From 062da366e0157c12dfcad792d133a291df7cb3fc Mon Sep 17 00:00:00 2001
From: Ulf Samuelsson
Date: Sun, 11 Jan 2009 21:13:02 +0000
Subject: Add buildall script for testing many/most packages separately with
build logs and documentation for this and mkpkg
---
docs/TESTING.html | 67 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 67 insertions(+)
create mode 100644 docs/TESTING.html
(limited to 'docs/TESTING.html')
diff --git a/docs/TESTING.html b/docs/TESTING.html
new file mode 100644
index 000000000..0f320ee96
--- /dev/null
+++ b/docs/TESTING.html
@@ -0,0 +1,67 @@
+
+
+Testing Buildroot for an Architecture
+
+
+
scripts/mkpkg script
+If you want to test the build of a single package you can use the mkpkg script.
+
+
+
$ scripts/mkpkg PACKAGE
+
+
+Will make the board, and save the result in a log file.
+The log file resides in
+
$ log/OK/PACKAGE.log.OK
+
+
+if the build succeeds and in
+
$ log/OK/PACKAGE.log.FAIL
+
+
+if it cannot complete.
+
+
+
+By creating an alias
+
alias mk=scripts/mkpkg
+
+
+it is enough to type
+
$ mk PACKAGE
+
+
+mkpkg will only print out the
{PACKAGE}......OK
or {PACKAGE}......FAIL
+depending on success or failure making it easy to get an overview
+of the status of this specific architecture.
+
+
+It is recommended to build a simple board before running the test
+to get some basic things done.
+
+
+
scripts/buildall.sh script
+
+
+By running this script you will run scripts/mkpkg on
+a lot of the packages available in Buildroot.
+
+
+You need to run the script while in the TOP directory.
+I.E: Where you typically run make.
+
+
+There are a few lacking, for no very good reason,
+but these can be easily added.
+
+
+Note that some packages will not build properly
+if you do not enable them using makeconfig.
+
+
+Examples are:
+
freetype
+socat
+
+
+
--
cgit v1.2.3-55-g7522