• Skip to sidebar navigation
  • Skip to content

Bitbucket

  • More
    ProjectsRepositories
  • Help
    • Online help
    • Learn Git
    • Welcome to Bitbucket
    • Keyboard shortcuts
  • Log In
Alexander Dahl
  1. Alexander Dahl

buildroot

Public
Actions
  • Clone
  • Compare

Learn more about cloning repositories

You have read-only access

Navigation
  • Source
  • Commits
  • Branches
  • All Branches Graph
  • Forks
  1. Alexander Dahl
  2. buildroot

Source

buildroot/docs/manual/configure-other-components.txt
Jörg KrauseJörg Krause committed 61f1578503216 Jul 2015
Raw file
Source viewDiff to previous
xxxxxxxxxx
 
1
// -*- mode:doc; -*-
2
// vim: set syntax=asciidoc:
3
​
4
== Configuration of other components
5
​
6
Before attempting to modify any of the components below, make sure you
7
have already configured Buildroot itself, and have enabled the
8
corresponding package.
9
​
10
BusyBox::
11
+
12
If you already have a BusyBox configuration file, you can directly
13
specify this file in the Buildroot configuration, using
14
+BR2_PACKAGE_BUSYBOX_CONFIG+. Otherwise, Buildroot will start from a
15
default BusyBox configuration file.
16
+
17
To make subsequent changes to the configuration, use +make
18
busybox-menuconfig+ to open the BusyBox configuration editor.
19
+
20
It is also possible to specify a BusyBox configuration file through an
21
environment variable, although this is not recommended. Refer to
22
xref:env-vars[] for more details.
23
​
24
uClibc::
25
+
26
Configuration of uClibc is done in the same way as for BusyBox. The
27
configuration variable to specify an existing configuration file is
28
+BR2_UCLIBC_CONFIG+. The command to make subsequent changes is +make
29
uclibc-menuconfig+.
30
​
31
Linux kernel::
32
+
33
If you already have a kernel configuration file, you can directly
34
specify this file in the Buildroot configuration, using
35
+BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG+.
36
+
37
If you do not yet have a kernel configuration file, you can either start
38
by specifying a defconfig in the Buildroot configuration, using
39
+BR2_LINUX_KERNEL_USE_DEFCONFIG+, or start by creating an empty file and
40
specifying it as custom configuration file, using
41
+BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG+.
42
+
43
To make subsequent changes to the configuration, use +make
44
linux-menuconfig+ to open the Linux configuration editor.
45
​
46
Barebox::
47
+
48
Configuration of Barebox is done in the same way as for the Linux
49
kernel. The corresponding configuration variables are
50
+BR2_TARGET_BAREBOX_USE_CUSTOM_CONFIG+ and
51
+BR2_TARGET_BAREBOX_USE_DEFCONFIG+. To open the configuration editor,
52
use +make barebox-menuconfig+.
53
​
54
U-Boot::
55
+
56
Configuration of U-Boot (version 2015.04 or newer) is done in the same
57
way as for the Linux kernel. The corresponding configuration variables
58
are +BR2_TARGET_UBOOT_USE_CUSTOM_CONFIG+ and
59
+BR2_TARGET_UBOOT_USE_DEFCONFIG+. To open the configuration editor,
60
use +make uboot-menuconfig+.
  • Git repository management for enterprise teams powered by Atlassian Bitbucket
  • Atlassian Bitbucket v6.7.2
  • Documentation
  • Request a feature
  • About
  • Contact Atlassian
Atlassian

Everything looks good. We'll let you know here if there's anything you should know about.