• 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/customize-directory-structure.txt
Thomas De SchampheleireThomas De Schampheleire committed 9e540c7517b18 Sep 2014
Raw file
Source viewDiff to previous
BR2_GLOBAL_PATCH_DIR="board/<company>/common/patches board/<company>/fooboard/patches"
 
1
// -*- mode:doc; -*-
2
// vim: set syntax=asciidoc:
3
​
4
[[customize-dir-structure]]
5
=== Recommended directory structure
6
​
7
When customizing Buildroot for your project, you will be creating one or
8
more project-specific files that need to be stored somewhere. While most
9
of these files could be placed in _any_ location as their path is to be
10
specified in the Buildroot configuration, the Buildroot developers
11
recommend a specific directory structure which is described in this
12
section.
13
​
14
Orthogonal to this directory structure, you can choose _where_ you place
15
this structure itself: either inside the Buildroot tree, or outside of
16
it using +BR2_EXTERNAL+. Both options are valid, the choice is up to you.
17
​
18
-----
19
+-- board/
20
|   +-- <company>/
21
|       +-- <boardname>/
22
|           +-- linux.config
23
|           +-- busybox.config
24
|           +-- <other configuration files>
25
|           +-- post_build.sh
26
|           +-- post_image.sh
27
|           +-- rootfs_overlay/
28
|           |   +-- etc/
29
|           |   +-- <some file>
30
|           +-- patches/
31
|               +-- foo/
32
|               |   +-- <some patch>
33
|               +-- libbar/
34
|                   +-- <some other patches>
35
|
36
+-- configs/
37
|   +-- <boardname>_defconfig
38
|
39
+-- package/
40
|   +-- <company>/
41
|       +-- Config.in (if not using BR2_EXTERNAL)
42
|       +-- <company>.mk (if not using BR2_EXTERNAL)
43
|       +-- package1/
44
|       |    +-- Config.in
45
|       |    +-- package1.mk
46
|       +-- package2/
47
|           +-- Config.in
48
|           +-- package2.mk
49
|
50
+-- Config.in (if using BR2_EXTERNAL)
51
+-- external.mk (if using BR2_EXTERNAL)
52
------
53
​
54
Details on the files shown above are given further in this chapter.
55
​
56
Note: if you choose to place this structure outside of the Buildroot
57
tree using +BR2_EXTERNAL+, the <company> and possibly <boardname>
58
components may be superfluous and can be left out.
59
​
60
==== Implementing layered customizations
61
​
62
It is quite common for a user to have several related projects that partly
63
need the same customizations. Instead of duplicating these
  • 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.