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