path: root/docs
diff options
authorWaldemar Brodkorb <>2017-03-05 02:52:58 (GMT)
committerWaldemar Brodkorb <>2017-03-05 03:27:06 (GMT)
commitdefd136511c34737ec9dcba5c8b0f027c2e2a0a3 (patch)
tree875877924ef3f080ee77d8b1fe405caaeab4f47f /docs
parent9cfbb9b905c1fa0aeb14d24ef7b66d61eaaa8381 (diff)
docs: add a working example for non-interactive usage
Diffstat (limited to 'docs')
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/common-usage.txt b/docs/common-usage.txt
index 28d04da..7cb1a9e 100644
--- a/docs/common-usage.txt
+++ b/docs/common-usage.txt
@@ -69,6 +69,7 @@ Environment variables
OpenADK also honors some environment variables, when they are passed
to +make+.
+* +ADK_APPLIANCE+, the appliance task you want to build
* +ADK_TARGET_ARCH+, the architecture of the target system
* +ADK_TARGET_SYSTEM+, the embedded target system name
* +ADK_TARGET_LIBC+, the C library for the target system
@@ -78,7 +79,7 @@ An example that creates a configuration file for Raspberry PI with all
software packages enabled, but not included in the resulting firmware image:
- $ make ADK_TARGET_ARCH=arm ADK_TARGET_SYSTEM=raspberry-pi ADK_TARGET_LIBC=musl allmodconfig
+ $ make ADK_APPLIANCE=new ADK_TARGET_ARCH=arm ADK_TARGET_SYSTEM=raspberry-pi ADK_TARGET_LIBC=musl allmodconfig
This is often used in the development process of a target system, to verify that