diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/common-usage.txt | 5 | ||||
| -rw-r--r-- | docs/using.txt | 4 |
2 files changed, 6 insertions, 3 deletions
diff --git a/docs/common-usage.txt b/docs/common-usage.txt index 4f41e8ad7..651b3bcad 100644 --- a/docs/common-usage.txt +++ b/docs/common-usage.txt @@ -69,12 +69,14 @@ Environment variables OpenADK also honors some environment variables, when they are passed to +make+. -* +ADK_APPLIANCE+, the appliance task you want to build +* +ADK_APPLIANCE+, the appliance task you want to build +* +ADK_CUSTOM_TASKS_DIR+, extra directory to fetch tasks from * +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 * +ADK_VERBOSE+, verbose build, when set to 1 + An example that creates a configuration file for Raspberry PI with all software packages enabled, but not included in the resulting firmware image: @@ -84,4 +86,3 @@ software packages enabled, but not included in the resulting firmware image: This is often used in the development process of a target system, to verify that all packages are compilable. - diff --git a/docs/using.txt b/docs/using.txt index d45babadd..96642f8e8 100644 --- a/docs/using.txt +++ b/docs/using.txt @@ -35,7 +35,9 @@ image::openadk-task.png[] If you want to compile some predefined appliance tasks, you can select it in +Tasks+. You can later simply add your own tasks, which is a collection of options, packages, -kernel modules or features, runtime configuration and more. +kernel modules or features, runtime configuration and more. They can either be placed +inside the +tasks+ directory or in your own custom directory that you pass via ++ADK_CUSTOM_TASKS_DIR+ to make. When you are ready exit and save. You can always redefine the configuration using +make menuconfig+. |