summaryrefslogtreecommitdiffstats
path: root/meta-yocto/conf/local.conf.sample
diff options
context:
space:
mode:
Diffstat (limited to 'meta-yocto/conf/local.conf.sample')
-rw-r--r--meta-yocto/conf/local.conf.sample252
1 files changed, 252 insertions, 0 deletions
diff --git a/meta-yocto/conf/local.conf.sample b/meta-yocto/conf/local.conf.sample
new file mode 100644
index 0000000..0111801
--- /dev/null
+++ b/meta-yocto/conf/local.conf.sample
@@ -0,0 +1,252 @@
1#
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.
8#
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.
13
14#
15# Parallelism Options
16#
17# These two options control how much parallelism BitBake should use. The first
18# option determines how many tasks bitbake should run in parallel:
19#
20#BB_NUMBER_THREADS ?= "4"
21#
22# Default to setting automatically based on cpu count
23BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
24#
25# The second option controls how many processes make should run in parallel when
26# running compile tasks:
27#
28#PARALLEL_MAKE ?= "-j 4"
29#
30# Default to setting automatically based on cpu count
31PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
32#
33# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
34# be appropriate for example.
35
36#
37# Machine Selection
38#
39# You need to select a specific machine to target the build with. There are a selection
40# of emulated machines available which can boot and run in the QEMU emulator:
41#
42#MACHINE ?= "qemuarm"
43#MACHINE ?= "qemumips"
44#MACHINE ?= "qemuppc"
45#MACHINE ?= "qemux86"
46#MACHINE ?= "qemux86-64"
47#
48# There are also the following hardware board target machines included for
49# demonstration purposes:
50#
51#MACHINE ?= "beaglebone"
52#MACHINE ?= "genericx86"
53#MACHINE ?= "genericx86-64"
54#MACHINE ?= "mpc8315e-rdb"
55#MACHINE ?= "edgerouter"
56#
57# This sets the default machine to be qemux86 if no other machine is selected:
58MACHINE ??= "qemux86"
59
60#
61# Where to place downloads
62#
63# During a first build the system will download many different source code tarballs
64# from various upstream projects. This can take a while, particularly if your network
65# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
66# can preserve this directory to speed up this part of subsequent builds. This directory
67# is safe to share between multiple builds on the same machine too.
68#
69# The default is a downloads directory under TOPDIR which is the build directory.
70#
71#DL_DIR ?= "${TOPDIR}/downloads"
72
73#
74# Where to place shared-state files
75#
76# BitBake has the capability to accelerate builds based on previously built output.
77# This is done using "shared state" files which can be thought of as cache objects
78# and this option determines where those files are placed.
79#
80# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
81# from these files if no changes were made to the configuration. If changes were made
82# to the configuration, only shared state files where the state was still valid would
83# be used (done using checksums).
84#
85# The default is a sstate-cache directory under TOPDIR.
86#
87#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
88
89#
90# Where to place the build output
91#
92# This option specifies where the bulk of the building work should be done and
93# where BitBake should place its temporary files and output. Keep in mind that
94# this includes the extraction and compilation of many applications and the toolchain
95# which can use Gigabytes of hard disk space.
96#
97# The default is a tmp directory under TOPDIR.
98#
99#TMPDIR = "${TOPDIR}/tmp"
100
101#
102# Default policy config
103#
104# The distribution setting controls which policy settings are used as defaults.
105# The default value is fine for general Yocto project use, at least initially.
106# Ultimately when creating custom policy, people will likely end up subclassing
107# these defaults.
108#
109DISTRO ?= "poky"
110# As an example of a subclass there is a "bleeding" edge policy configuration
111# where many versions are set to the absolute latest code from the upstream
112# source control systems. This is just mentioned here as an example, its not
113# useful to most new users.
114# DISTRO ?= "poky-bleeding"
115
116#
117# Package Management configuration
118#
119# This variable lists which packaging formats to enable. Multiple package backends
120# can be enabled at once and the first item listed in the variable will be used
121# to generate the root filesystems.
122# Options are:
123# - 'package_deb' for debian style deb files
124# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
125# - 'package_rpm' for rpm style packages
126# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
127# We default to rpm:
128PACKAGE_CLASSES ?= "package_rpm"
129
130#
131# SDK/ADT target architecture
132#
133# This variable specifies the architecture to build SDK/ADT items for and means
134# you can build the SDK packages for architectures other than the machine you are
135# running the build on (i.e. building i686 packages on an x86_64 host).
136# Supported values are i686 and x86_64
137#SDKMACHINE ?= "i686"
138
139#
140# Extra image configuration defaults
141#
142# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
143# images. Some of these options are added to certain image types automatically. The
144# variable can contain the following options:
145# "dbg-pkgs" - add -dbg packages for all installed packages
146# (adds symbol information for debugging/profiling)
147# "dev-pkgs" - add -dev packages for all installed packages
148# (useful if you want to develop against libs in the image)
149# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
150# (useful if you want to run the package test suites)
151# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
152# "tools-debug" - add debugging tools (gdb, strace)
153# "eclipse-debug" - add Eclipse remote debugging support
154# "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind)
155# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
156# "debug-tweaks" - make an image suitable for development
157# e.g. ssh root access has a blank password
158# There are other application targets that can be used here too, see
159# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
160# We default to enabling the debugging tweaks.
161EXTRA_IMAGE_FEATURES = "debug-tweaks"
162
163#
164# Additional image features
165#
166# The following is a list of additional classes to use when building images which
167# enable extra features. Some available options which can be included in this variable
168# are:
169# - 'buildstats' collect build statistics
170# - 'image-mklibs' to reduce shared library files size for an image
171# - 'image-prelink' in order to prelink the filesystem image
172# - 'image-swab' to perform host system intrusion detection
173# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
174# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
175USER_CLASSES ?= "buildstats image-mklibs image-prelink"
176
177#
178# Runtime testing of images
179#
180# The build system can test booting virtual machine images under qemu (an emulator)
181# after any root filesystems are created and run tests against those images. To
182# enable this uncomment this line. See classes/testimage(-auto).bbclass for
183# further details.
184#TEST_IMAGE = "1"
185#
186# Interactive shell configuration
187#
188# Under certain circumstances the system may need input from you and to do this it
189# can launch an interactive shell. It needs to do this since the build is
190# multithreaded and needs to be able to handle the case where more than one parallel
191# process may require the user's attention. The default is iterate over the available
192# terminal types to find one that works.
193#
194# Examples of the occasions this may happen are when resolving patches which cannot
195# be applied, to use the devshell or the kernel menuconfig
196#
197# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
198# Note: currently, Konsole support only works for KDE 3.x due to the way
199# newer Konsole versions behave
200#OE_TERMINAL = "auto"
201# By default disable interactive patch resolution (tasks will just fail instead):
202PATCHRESOLVE = "noop"
203
204#
205# Disk Space Monitoring during the build
206#
207# Monitor the disk space during the build. If there is less that 1GB of space or less
208# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
209# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
210# of the build. The reason for this is that running completely out of space can corrupt
211# files and damages the build in ways which may not be easily recoverable.
212BB_DISKMON_DIRS = "\
213 STOPTASKS,${TMPDIR},1G,100K \
214 STOPTASKS,${DL_DIR},1G,100K \
215 STOPTASKS,${SSTATE_DIR},1G,100K \
216 ABORT,${TMPDIR},100M,1K \
217 ABORT,${DL_DIR},100M,1K \
218 ABORT,${SSTATE_DIR},100M,1K"
219
220#
221# Shared-state files from other locations
222#
223# As mentioned above, shared state files are prebuilt cache data objects which can
224# used to accelerate build time. This variable can be used to configure the system
225# to search other mirror locations for these objects before it builds the data itself.
226#
227# This can be a filesystem directory, or a remote url such as http or ftp. These
228# would contain the sstate-cache results from previous builds (possibly from other
229# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
230# cache locations to check for the shared objects.
231# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
232# at the end as shown in the examples below. This will be substituted with the
233# correct path within the directory structure.
234#SSTATE_MIRRORS ?= "\
235#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
236#file://.* file:///some/local/dir/sstate/PATH"
237
238
239#
240# Qemu configuration
241#
242# By default qemu will build with a builtin VNC server where graphical output can be
243# seen. The two lines below enable the SDL backend too. This assumes there is a
244# libsdl library available on your build system.
245PACKAGECONFIG_pn-qemu-native = "sdl"
246ASSUME_PROVIDED += "libsdl-native"
247
248
249# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
250# track the version of this file when it was generated. This can safely be ignored if
251# this doesn't mean anything to you.
252CONF_VERSION = "1"