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"
23 #MACHINE ?= "qemumips64"
26 #MACHINE ?= "qemux86-64"
28 # There are also the following hardware board target machines included for
29 # demonstration purposes:
31 #MACHINE ?= "beaglebone-yocto"
32 #MACHINE ?= "genericx86"
33 #MACHINE ?= "genericx86-64"
34 #MACHINE ?= "mpc8315e-rdb"
35 #MACHINE ?= "edgerouter"
37 # This sets the default machine to be qemux86-64 if no other machine is selected:
38 MACHINE ??= "qemux86-64"
41 # Where to place downloads
43 # During a first build the system will download many different source code tarballs
44 # from various upstream projects. This can take a while, particularly if your network
45 # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
46 # can preserve this directory to speed up this part of subsequent builds. This directory
47 # is safe to share between multiple builds on the same machine too.
49 # The default is a downloads directory under TOPDIR which is the build directory.
51 #DL_DIR ?= "${TOPDIR}/downloads"
54 # Where to place shared-state files
56 # BitBake has the capability to accelerate builds based on previously built output.
57 # This is done using "shared state" files which can be thought of as cache objects
58 # and this option determines where those files are placed.
60 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
61 # from these files if no changes were made to the configuration. If changes were made
62 # to the configuration, only shared state files where the state was still valid would
63 # be used (done using checksums).
65 # The default is a sstate-cache directory under TOPDIR.
67 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
70 # Where to place the build output
72 # This option specifies where the bulk of the building work should be done and
73 # where BitBake should place its temporary files and output. Keep in mind that
74 # this includes the extraction and compilation of many applications and the toolchain
75 # which can use Gigabytes of hard disk space.
77 # The default is a tmp directory under TOPDIR.
79 #TMPDIR = "${TOPDIR}/tmp"
82 # Default policy config
84 # The distribution setting controls which policy settings are used as defaults.
85 # The default value is fine for general Yocto project use, at least initially.
86 # Ultimately when creating custom policy, people will likely end up subclassing
90 # As an example of a subclass there is a "bleeding" edge policy configuration
91 # where many versions are set to the absolute latest code from the upstream
92 # source control systems. This is just mentioned here as an example, its not
93 # useful to most new users.
94 # DISTRO ?= "poky-bleeding"
97 # Package Management configuration
99 # This variable lists which packaging formats to enable. Multiple package backends
100 # can be enabled at once and the first item listed in the variable will be used
101 # to generate the root filesystems.
103 # - 'package_deb' for debian style deb files
104 # - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
105 # - 'package_rpm' for rpm style packages
106 # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
108 PACKAGE_CLASSES ?= "package_rpm"
111 # SDK target architecture
113 # This variable specifies the architecture to build SDK items for and means
114 # you can build the SDK packages for architectures other than the machine you are
115 # running the build on (i.e. building i686 packages on an x86_64 host).
116 # Supported values are i686 and x86_64
117 #SDKMACHINE ?= "i686"
120 # Extra image configuration defaults
122 # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
123 # images. Some of these options are added to certain image types automatically. The
124 # variable can contain the following options:
125 # "dbg-pkgs" - add -dbg packages for all installed packages
126 # (adds symbol information for debugging/profiling)
127 # "src-pkgs" - add -src packages for all installed packages
128 # (adds source code for debugging)
129 # "dev-pkgs" - add -dev packages for all installed packages
130 # (useful if you want to develop against libs in the image)
131 # "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
132 # (useful if you want to run the package test suites)
133 # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
134 # "tools-debug" - add debugging tools (gdb, strace)
135 # "eclipse-debug" - add Eclipse remote debugging support
136 # "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
137 # "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
138 # "debug-tweaks" - make an image suitable for development
139 # e.g. ssh root access has a blank password
140 # There are other application targets that can be used here too, see
141 # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
142 # We default to enabling the debugging tweaks.
143 EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
146 # Additional image features
148 # The following is a list of additional classes to use when building images which
149 # enable extra features. Some available options which can be included in this variable
151 # - 'buildstats' collect build statistics
152 USER_CLASSES ?= "buildstats"
155 # Runtime testing of images
157 # The build system can test booting virtual machine images under qemu (an emulator)
158 # after any root filesystems are created and run tests against those images. It can also
159 # run tests against any SDK that are built. To enable this uncomment these lines.
160 # See classes/test{image,sdk}.bbclass for further details.
161 #IMAGE_CLASSES += "testimage testsdk"
162 #TESTIMAGE_AUTO:qemuall = "1"
165 # Interactive shell configuration
167 # Under certain circumstances the system may need input from you and to do this it
168 # can launch an interactive shell. It needs to do this since the build is
169 # multithreaded and needs to be able to handle the case where more than one parallel
170 # process may require the user's attention. The default is iterate over the available
171 # terminal types to find one that works.
173 # Examples of the occasions this may happen are when resolving patches which cannot
174 # be applied, to use the devshell or the kernel menuconfig
176 # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
177 # Note: currently, Konsole support only works for KDE 3.x due to the way
178 # newer Konsole versions behave
179 #OE_TERMINAL = "auto"
180 # By default disable interactive patch resolution (tasks will just fail instead):
181 PATCHRESOLVE = "noop"
184 # Disk Space Monitoring during the build
186 # Monitor the disk space during the build. If there is less that 1GB of space or less
187 # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
188 # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard halt
189 # of the build. The reason for this is that running completely out of space can corrupt
190 # files and damages the build in ways which may not be easily recoverable.
191 # It's necesary to monitor /tmp, if there is no space left the build will fail
192 # with very exotic errors.
193 BB_DISKMON_DIRS ??= "\
194 STOPTASKS,${TMPDIR},1G,100K \
195 STOPTASKS,${DL_DIR},1G,100K \
196 STOPTASKS,${SSTATE_DIR},1G,100K \
197 STOPTASKS,/tmp,100M,100K \
198 HALT,${TMPDIR},100M,1K \
199 HALT,${DL_DIR},100M,1K \
200 HALT,${SSTATE_DIR},100M,1K \
204 # Shared-state files from other locations
206 # As mentioned above, shared state files are prebuilt cache data objects which can
207 # used to accelerate build time. This variable can be used to configure the system
208 # to search other mirror locations for these objects before it builds the data itself.
210 # This can be a filesystem directory, or a remote url such as http or ftp. These
211 # would contain the sstate-cache results from previous builds (possibly from other
212 # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
213 # cache locations to check for the shared objects.
214 # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
215 # at the end as shown in the examples below. This will be substituted with the
216 # correct path within the directory structure.
217 #SSTATE_MIRRORS ?= "\
218 #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
219 #file://.* file:///some/local/dir/sstate/PATH"
222 # AGL Project SState Mirror
224 # The AGL Project has prebuilt artefacts available for its releases, you can enable
225 # use of these by uncommenting the following line. This will mean the build uses
226 # the network to check for artefacts at the start of builds, which does slow it down
227 # equally, it will also speed up the builds by not having to build things if they are
228 # present in the cache. It assumes you can download something faster than you can build it
229 # which will depend on your network.
231 #SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"
233 #SSTATE_MIRRORS += "file://.* http://download.automotivelinux.org/sstate-mirror/${AGL_BRANCH}/${DEFAULTTUNE}/PATH;downloadfilename=PATH"
238 # By default native qemu will build with a builtin VNC server where graphical output can be
239 # seen. The line below enables the SDL UI frontend too.
240 PACKAGECONFIG:append:pn-qemu-system-native = " sdl"
241 # By default libsdl2-native will be built, if you want to use your host's libSDL instead of
242 # the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
243 #ASSUME_PROVIDED += "libsdl2-native"
245 # You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
246 # a handy set of menus for controlling the emulator.
247 #PACKAGECONFIG:append:pn-qemu-system-native = " gtk+"
250 # Parallelism Options
252 # These two options control how much parallelism BitBake should use. The first
253 # option determines how many tasks bitbake should run in parallel:
255 #BB_NUMBER_THREADS ?= "4"
257 # Default to setting automatically based on cpu count
258 #BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
260 # The second option controls how many processes make should run in parallel when
261 # running compile tasks:
263 #PARALLEL_MAKE ?= "-j 4"
265 # Default to setting automatically based on cpu count
266 #PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
268 # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
269 # be appropriate for example.
274 # Enable support for automatically running a local hash equivalence server and
275 # instruct bitbake to use a hash equivalence aware signature generator. Hash
276 # equivalence improves reuse of sstate by detecting when a given sstate
277 # artifact can be reused as equivalent, even if the current task hash doesn't
278 # match the one that generated the artifact.
280 # A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
283 #BB_HASHSERVE = "auto"
284 #BB_SIGNATURE_HANDLER = "OEEquivHash"
286 # online/upstream r/o
287 #AGL_HOST_HASHSERV = "prserv.automotivelinux.org"
288 #BB_SIGNATURE_HANDLER = "OEEquivHash"
289 #BB_HASHSERVE = "auto"
290 #BB_HASHSERVE_UPSTREAM = "${AGL_HOST_HASHSERV}:8888"
292 # The network based PR service host and port
293 # Uncomment the following lines to enable PRservice.
294 # Set PRSERV_HOST to 'localhost:0' to automatically
295 # start local PRService.
296 # Set to other values to use remote PRService.
297 #PRSERV_HOST = "localhost:0"
299 # r/o upstream prserv
300 #AGL_HOST_PRSERV = "prserv.automotivelinux.org"
301 #PRSERV_HOST = "prserv.automotivelinux.org:8686"
304 # Archive the source and put them to ${DEPLOY_DIR}/sources/.
306 #INHERIT += "archiver"
308 # The tarball for the patched source will be created by default, and you
309 # can configure the archiver as follow:
311 # Create archive for:
312 # 1) original (or unpacked) source:
313 #ARCHIVER_MODE[src] = "original"
314 # 2) patched source: (default)
315 #ARCHIVER_MODE[src] = "patched"
316 # 3) configured source:
317 #ARCHIVER_MODE[src] = "configured"
319 # 4) the patches between do_unpack and do_patch:
320 #ARCHIVER_MODE[diff] = "1"
321 # set the files that you'd like to exclude from the diff:
322 #ARCHIVER_MODE[diff-exclude] ?= ".pc autom4te.cache patches"
324 # 5) the environment data, similar to 'bitbake -e recipe':
325 #ARCHIVER_MODE[dumpdata] = "1"
327 # 6) the recipe (.bb and .inc):
328 #ARCHIVER_MODE[recipe] = "1"
330 # 7) Whether output the .src.rpm package:
331 #ARCHIVER_MODE[srpm] = "1"
333 # 8) Filter the license, the recipe whose license in
334 # COPYLEFT_LICENSE_INCLUDE will be included, and in
335 # COPYLEFT_LICENSE_EXCLUDE will be excluded.
336 #COPYLEFT_LICENSE_INCLUDE = 'GPL* LGPL*'
337 #COPYLEFT_LICENSE_EXCLUDE = 'CLOSED Proprietary'
339 # 9) Config the recipe type that will be archived, the type can be
340 # target, native, nativesdk, cross, crosssdk and cross-canadian,
341 # you can set one or more types. Archive all types by default.
342 #COPYLEFT_RECIPE_TYPES = 'target'
346 # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
347 # track the version of this file when it was generated. This can safely be ignored if
348 # this doesn't mean anything to you.