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