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