2 # This file is your local configuration file and is where all local user settings
3 # are placed. The comments in this file give some guide to the options a new user
4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
7 # but new users likely won't need any of them initially.
9 # Lines starting with the '#' character are commented out and in some cases the
10 # default values are provided as comments to show people example syntax. Enabling
11 # the option is a question of removing the # character and making any change to the
12 # variable as required.
17 # You need to select a specific machine to target the build with. There are a selection
18 # of emulated machines available which can boot and run in the QEMU emulator:
21 #MACHINE ?= "qemuarm64"
22 #MACHINE ?= "qemumips"
25 #MACHINE ?= "qemux86-64"
27 # There are also the following hardware board target machines included for
28 # demonstration purposes:
30 #MACHINE ?= "beaglebone"
31 #MACHINE ?= "genericx86"
32 #MACHINE ?= "genericx86-64"
33 #MACHINE ?= "mpc8315e-rdb"
34 #MACHINE ?= "edgerouter"
36 # This sets the default machine to be qemux86 if no other machine is selected:
40 # Where to place downloads
42 # During a first build the system will download many different source code tarballs
43 # from various upstream projects. This can take a while, particularly if your network
44 # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
45 # can preserve this directory to speed up this part of subsequent builds. This directory
46 # is safe to share between multiple builds on the same machine too.
48 # The default is a downloads directory under TOPDIR which is the build directory.
50 #DL_DIR ?= "${TOPDIR}/downloads"
53 # Where to place shared-state files
55 # BitBake has the capability to accelerate builds based on previously built output.
56 # This is done using "shared state" files which can be thought of as cache objects
57 # and this option determines where those files are placed.
59 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
60 # from these files if no changes were made to the configuration. If changes were made
61 # to the configuration, only shared state files where the state was still valid would
62 # be used (done using checksums).
64 # The default is a sstate-cache directory under TOPDIR.
66 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
69 # Where to place the build output
71 # This option specifies where the bulk of the building work should be done and
72 # where BitBake should place its temporary files and output. Keep in mind that
73 # this includes the extraction and compilation of many applications and the toolchain
74 # which can use Gigabytes of hard disk space.
76 # The default is a tmp directory under TOPDIR.
78 #TMPDIR = "${TOPDIR}/tmp"
81 # Default policy config
83 # The distribution setting controls which policy settings are used as defaults.
84 # The default value is fine for general Yocto project use, at least initially.
85 # Ultimately when creating custom policy, people will likely end up subclassing
89 # As an example of a subclass there is a "bleeding" edge policy configuration
90 # where many versions are set to the absolute latest code from the upstream
91 # source control systems. This is just mentioned here as an example, its not
92 # useful to most new users.
93 # DISTRO ?= "poky-bleeding"
96 # Package Management configuration
98 # This variable lists which packaging formats to enable. Multiple package backends
99 # can be enabled at once and the first item listed in the variable will be used
100 # to generate the root filesystems.
102 # - 'package_deb' for debian style deb files
103 # - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
104 # - 'package_rpm' for rpm style packages
105 # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
107 PACKAGE_CLASSES ?= "package_rpm"
110 # SDK/ADT target architecture
112 # This variable specifies the architecture to build SDK/ADT items for and means
113 # you can build the SDK packages for architectures other than the machine you are
114 # running the build on (i.e. building i686 packages on an x86_64 host).
115 # Supported values are i686 and x86_64
116 #SDKMACHINE ?= "i686"
119 # Extra image configuration defaults
121 # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
122 # images. Some of these options are added to certain image types automatically. The
123 # variable can contain the following options:
124 # "dbg-pkgs" - add -dbg packages for all installed packages
125 # (adds symbol information for debugging/profiling)
126 # "dev-pkgs" - add -dev packages for all installed packages
127 # (useful if you want to develop against libs in the image)
128 # "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
129 # (useful if you want to run the package test suites)
130 # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
131 # "tools-debug" - add debugging tools (gdb, strace)
132 # "eclipse-debug" - add Eclipse remote debugging support
133 # "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind)
134 # "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
135 # "debug-tweaks" - make an image suitable for development
136 # e.g. ssh root access has a blank password
137 # There are other application targets that can be used here too, see
138 # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
139 # We default to enabling the debugging tweaks.
140 EXTRA_IMAGE_FEATURES = "debug-tweaks"
143 # Additional image features
145 # The following is a list of additional classes to use when building images which
146 # enable extra features. Some available options which can be included in this variable
148 # - 'buildstats' collect build statistics
149 # - 'image-mklibs' to reduce shared library files size for an image
150 # - 'image-prelink' in order to prelink the filesystem image
151 # - 'image-swab' to perform host system intrusion detection
152 # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
153 # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
154 # NOTE: image-prelink is currently broken due to problems with the prelinker. It is advised
155 # that you do NOT run the prelinker at this time.
156 USER_CLASSES ?= "buildstats image-mklibs"
159 # Runtime testing of images
161 # The build system can test booting virtual machine images under qemu (an emulator)
162 # after any root filesystems are created and run tests against those images. To
163 # enable this uncomment this line. See classes/testimage(-auto).bbclass for
167 # Interactive shell configuration
169 # Under certain circumstances the system may need input from you and to do this it
170 # can launch an interactive shell. It needs to do this since the build is
171 # multithreaded and needs to be able to handle the case where more than one parallel
172 # process may require the user's attention. The default is iterate over the available
173 # terminal types to find one that works.
175 # Examples of the occasions this may happen are when resolving patches which cannot
176 # be applied, to use the devshell or the kernel menuconfig
178 # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
179 # Note: currently, Konsole support only works for KDE 3.x due to the way
180 # newer Konsole versions behave
181 #OE_TERMINAL = "auto"
182 # By default disable interactive patch resolution (tasks will just fail instead):
183 PATCHRESOLVE = "noop"
186 # Disk Space Monitoring during the build
188 # Monitor the disk space during the build. If there is less that 1GB of space or less
189 # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
190 # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
191 # of the build. The reason for this is that running completely out of space can corrupt
192 # files and damages the build in ways which may not be easily recoverable.
193 # It's necesary to monitor /tmp, if there is no space left the build will fail
194 # with very exotic errors.
196 STOPTASKS,${TMPDIR},1G,100K \
197 STOPTASKS,${DL_DIR},1G,100K \
198 STOPTASKS,${SSTATE_DIR},1G,100K \
199 STOPTASKS,/tmp,100M,100K \
200 ABORT,${TMPDIR},100M,1K \
201 ABORT,${DL_DIR},100M,1K \
202 ABORT,${SSTATE_DIR},100M,1K \
206 # Shared-state files from other locations
208 # As mentioned above, shared state files are prebuilt cache data objects which can
209 # used to accelerate build time. This variable can be used to configure the system
210 # to search other mirror locations for these objects before it builds the data itself.
212 # This can be a filesystem directory, or a remote url such as http or ftp. These
213 # would contain the sstate-cache results from previous builds (possibly from other
214 # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
215 # cache locations to check for the shared objects.
216 # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
217 # at the end as shown in the examples below. This will be substituted with the
218 # correct path within the directory structure.
219 #SSTATE_MIRRORS ?= "\
220 #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
221 #file://.* file:///some/local/dir/sstate/PATH"
227 # By default qemu will build with a builtin VNC server where graphical output can be
228 # seen. The two lines below enable the SDL backend too. By default libsdl-native will
229 # be built, if you want to use your host's libSDL instead of the minimal libsdl built
230 # by libsdl-native then uncomment the ASSUME_PROVIDED line below.
231 PACKAGECONFIG_append_pn-qemu-native = " sdl"
232 PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
233 #ASSUME_PROVIDED += "libsdl-native"
236 # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
237 # track the version of this file when it was generated. This can safely be ignored if
238 # this doesn't mean anything to you.