summaryrefslogtreecommitdiff
path: root/docs/customize-busybox-config.txt
blob: 070a0ca1e19aacaf12ef055275865f0c990dabf7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:

[[busybox-custom]]
Customizing the Busybox configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

http://www.busybox.net/[Busybox] is very configurable, and you may
want to customize it. You can just configure it via +Package selection+,
+Base System+, +Busybox Configuration+. The menu based busybox configuration
is mostly integrated into OpenADK. There are some options, which are not
available and not supported. If you need to, you can change the defaults
in +package/busybox/config+ and regenerate your OpenADK configuration.

A change in the busybox configuration will rebuild the busybox package. If you
choose another implementation of f.e. tar, which is provided by default from
busybox, tar in busybox will be deactivated and the package will be
automatically rebuilded, so that your resulting firmware images or archives
will only contain a single tar program. Obviously just the one you have
selected.