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