|
| 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 | +# Machine Selection |
| 16 | +# |
| 17 | +MACHINE ??= "ventura" |
| 18 | + |
| 19 | +# |
| 20 | +# Where to place downloads |
| 21 | +# |
| 22 | +# During a first build the system will download many different source code tarballs |
| 23 | +# from various upstream projects. This can take a while, particularly if your network |
| 24 | +# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you |
| 25 | +# can preserve this directory to speed up this part of subsequent builds. This directory |
| 26 | +# is safe to share between multiple builds on the same machine too. |
| 27 | +# |
| 28 | +# The default is a downloads directory under TOPDIR which is the build directory. |
| 29 | +# |
| 30 | +#DL_DIR ?= "${TOPDIR}/downloads" |
| 31 | + |
| 32 | +# |
| 33 | +# Where to place shared-state files |
| 34 | +# |
| 35 | +# BitBake has the capability to accelerate builds based on previously built output. |
| 36 | +# This is done using "shared state" files which can be thought of as cache objects |
| 37 | +# and this option determines where those files are placed. |
| 38 | +# |
| 39 | +# You can wipe out TMPDIR leaving this directory intact and the build would regenerate |
| 40 | +# from these files if no changes were made to the configuration. If changes were made |
| 41 | +# to the configuration, only shared state files where the state was still valid would |
| 42 | +# be used (done using checksums). |
| 43 | +# |
| 44 | +# The default is a sstate-cache directory under TOPDIR. |
| 45 | +# |
| 46 | +#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" |
| 47 | + |
| 48 | +# |
| 49 | +# Where to place the build output |
| 50 | +# |
| 51 | +# This option specifies where the bulk of the building work should be done and |
| 52 | +# where BitBake should place its temporary files and output. Keep in mind that |
| 53 | +# this includes the extraction and compilation of many applications and the toolchain |
| 54 | +# which can use Gigabytes of hard disk space. |
| 55 | +# |
| 56 | +# The default is a tmp directory under TOPDIR. |
| 57 | +# |
| 58 | +#TMPDIR = "${TOPDIR}/tmp" |
| 59 | + |
| 60 | +# |
| 61 | +# Default policy config |
| 62 | +# |
| 63 | +# The distribution setting controls which policy settings are used as defaults. |
| 64 | +# The default value is fine for general Yocto project use, at least initially. |
| 65 | +# Ultimately when creating custom policy, people will likely end up subclassing |
| 66 | +# these defaults. |
| 67 | +# |
| 68 | +DISTRO ?= "openbmc-phosphor" |
| 69 | +# As an example of a subclass there is a "bleeding" edge policy configuration |
| 70 | +# where many versions are set to the absolute latest code from the upstream |
| 71 | +# source control systems. This is just mentioned here as an example, its not |
| 72 | +# useful to most new users. |
| 73 | +# DISTRO ?= "poky-bleeding" |
| 74 | + |
| 75 | +# |
| 76 | +# Package Management configuration |
| 77 | +# |
| 78 | +# This variable lists which packaging formats to enable. Multiple package backends |
| 79 | +# can be enabled at once and the first item listed in the variable will be used |
| 80 | +# to generate the root filesystems. |
| 81 | +# Options are: |
| 82 | +# - 'package_deb' for debian style deb files |
| 83 | +# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) |
| 84 | +# - 'package_rpm' for rpm style packages |
| 85 | +# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" |
| 86 | +# We default to ipk: |
| 87 | +PACKAGE_CLASSES ?= "package_ipk" |
| 88 | + |
| 89 | +# |
| 90 | +# SDK target architecture |
| 91 | +# |
| 92 | +# This variable specifies the architecture to build SDK items for and means |
| 93 | +# you can build the SDK packages for architectures other than the machine you are |
| 94 | +# running the build on (i.e. building i686 packages on an x86_64 host). |
| 95 | +# Supported values are i686, x86_64, aarch64 |
| 96 | +#SDKMACHINE ?= "i686" |
| 97 | + |
| 98 | +SANITY_TESTED_DISTROS:append ?= " *" |
| 99 | + |
| 100 | +# |
| 101 | +# Extra image configuration defaults |
| 102 | +# |
| 103 | +# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated |
| 104 | +# images. Some of these options are added to certain image types automatically. The |
| 105 | +# variable can contain the following options: |
| 106 | +# "dbg-pkgs" - add -dbg packages for all installed packages |
| 107 | +# (adds symbol information for debugging/profiling) |
| 108 | +# "src-pkgs" - add -src packages for all installed packages |
| 109 | +# (adds source code for debugging) |
| 110 | +# "dev-pkgs" - add -dev packages for all installed packages |
| 111 | +# (useful if you want to develop against libs in the image) |
| 112 | +# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages |
| 113 | +# (useful if you want to run the package test suites) |
| 114 | +# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) |
| 115 | +# "tools-debug" - add debugging tools (gdb, strace) |
| 116 | +# "eclipse-debug" - add Eclipse remote debugging support |
| 117 | +# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) |
| 118 | +# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) |
| 119 | +# "debug-tweaks" - make an image suitable for development |
| 120 | +# e.g. ssh root access has a blank password |
| 121 | +# There are other application targets that can be used here too, see |
| 122 | +# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. |
| 123 | +# We default to enabling the debugging tweaks. |
| 124 | +EXTRA_IMAGE_FEATURES ?= "debug-tweaks" |
| 125 | + |
| 126 | +# |
| 127 | +# Additional image features |
| 128 | +# |
| 129 | +# The following is a list of additional classes to use when building images which |
| 130 | +# enable extra features. Some available options which can be included in this variable |
| 131 | +# are: |
| 132 | +# - 'buildstats' collect build statistics |
| 133 | +USER_CLASSES ?= "buildstats" |
| 134 | + |
| 135 | +# |
| 136 | +# Runtime testing of images |
| 137 | +# |
| 138 | +# The build system can test booting virtual machine images under qemu (an emulator) |
| 139 | +# after any root filesystems are created and run tests against those images. It can also |
| 140 | +# run tests against any SDK that are built. To enable this uncomment these lines. |
| 141 | +# See classes/test{image,sdk}.bbclass for further details. |
| 142 | +#IMAGE_CLASSES += "testimage testsdk" |
| 143 | +#TESTIMAGE_AUTO_qemuall = "1" |
| 144 | + |
| 145 | +# |
| 146 | +# Interactive shell configuration |
| 147 | +# |
| 148 | +# Under certain circumstances the system may need input from you and to do this it |
| 149 | +# can launch an interactive shell. It needs to do this since the build is |
| 150 | +# multithreaded and needs to be able to handle the case where more than one parallel |
| 151 | +# process may require the user's attention. The default is iterate over the available |
| 152 | +# terminal types to find one that works. |
| 153 | +# |
| 154 | +# Examples of the occasions this may happen are when resolving patches which cannot |
| 155 | +# be applied, to use the devshell or the kernel menuconfig |
| 156 | +# |
| 157 | +# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none |
| 158 | +# Note: currently, Konsole support only works for KDE 3.x due to the way |
| 159 | +# newer Konsole versions behave |
| 160 | +#OE_TERMINAL = "auto" |
| 161 | +# By default disable interactive patch resolution (tasks will just fail instead): |
| 162 | +PATCHRESOLVE = "noop" |
| 163 | + |
| 164 | +# |
| 165 | +# Disk Space Monitoring during the build |
| 166 | +# |
| 167 | +# Monitor the disk space during the build. If there is less that 1GB of space or less |
| 168 | +# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully |
| 169 | +# shutdown the build. If there is less than 100MB or 1K inodes, perform a hard abort |
| 170 | +# of the build. The reason for this is that running completely out of space can corrupt |
| 171 | +# files and damages the build in ways which may not be easily recoverable. |
| 172 | +# It's necessary to monitor /tmp, if there is no space left the build will fail |
| 173 | +# with very exotic errors. |
| 174 | +BB_DISKMON_DIRS ??= "\ |
| 175 | + STOPTASKS,${TMPDIR},1G,100K \ |
| 176 | + STOPTASKS,${DL_DIR},1G,100K \ |
| 177 | + STOPTASKS,${SSTATE_DIR},1G,100K \ |
| 178 | + STOPTASKS,/tmp,100M,100K \ |
| 179 | + HALT,${TMPDIR},100M,1K \ |
| 180 | + HALT,${DL_DIR},100M,1K \ |
| 181 | + HALT,${SSTATE_DIR},100M,1K \ |
| 182 | + HALT,/tmp,10M,1K" |
| 183 | + |
| 184 | +# |
| 185 | +# Shared-state files from other locations |
| 186 | +# |
| 187 | +# As mentioned above, shared state files are prebuilt cache data objects which can be |
| 188 | +# used to accelerate build time. This variable can be used to configure the system |
| 189 | +# to search other mirror locations for these objects before it builds the data itself. |
| 190 | +# |
| 191 | +# This can be a filesystem directory, or a remote url such as http or ftp. These |
| 192 | +# would contain the sstate-cache results from previous builds (possibly from other |
| 193 | +# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the |
| 194 | +# cache locations to check for the shared objects. |
| 195 | +# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH |
| 196 | +# at the end as shown in the examples below. This will be substituted with the |
| 197 | +# correct path within the directory structure. |
| 198 | +#SSTATE_MIRRORS ?= "\ |
| 199 | +#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ |
| 200 | +#file://.* file:///some/local/dir/sstate/PATH" |
| 201 | + |
| 202 | +# |
| 203 | +# Yocto Project SState Mirror |
| 204 | +# |
| 205 | +# The Yocto Project has prebuilt artefacts available for its releases, you can enable |
| 206 | +# use of these by uncommenting the following line. This will mean the build uses |
| 207 | +# the network to check for artefacts at the start of builds, which does slow it down |
| 208 | +# equally, it will also speed up the builds by not having to build things if they are |
| 209 | +# present in the cache. It assumes you can download something faster than you can build it |
| 210 | +# which will depend on your network. |
| 211 | +# |
| 212 | +#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" |
| 213 | + |
| 214 | +# |
| 215 | +# Qemu configuration |
| 216 | +# |
| 217 | +# By default native qemu will build with a builtin VNC server where graphical output can be |
| 218 | +# seen. The line below enables the SDL UI frontend too. |
| 219 | +PACKAGECONFIG:append:pn-qemu-system-native = " sdl" |
| 220 | +# By default libsdl2-native will be built, if you want to use your host's libSDL instead of |
| 221 | +# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below. |
| 222 | +#ASSUME_PROVIDED += "libsdl2-native" |
| 223 | + |
| 224 | +# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds |
| 225 | +# a handy set of menus for controlling the emulator. |
| 226 | +#PACKAGECONFIG:append:pn-qemu-system-native = " gtk+" |
| 227 | + |
| 228 | +# |
| 229 | +# Hash Equivalence |
| 230 | +# |
| 231 | +# Enable support for automatically running a local hash equivalence server and |
| 232 | +# instruct bitbake to use a hash equivalence aware signature generator. Hash |
| 233 | +# equivalence improves reuse of sstate by detecting when a given sstate |
| 234 | +# artifact can be reused as equivalent, even if the current task hash doesn't |
| 235 | +# match the one that generated the artifact. |
| 236 | +# |
| 237 | +# A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format |
| 238 | +# |
| 239 | +#BB_HASHSERVE = "auto" |
| 240 | +#BB_SIGNATURE_HANDLER = "OEEquivHash" |
| 241 | + |
| 242 | +# |
| 243 | +# Memory Resident Bitbake |
| 244 | +# |
| 245 | +# Bitbake's server component can stay in memory after the UI for the current command |
| 246 | +# has completed. This means subsequent commands can run faster since there is no need |
| 247 | +# for bitbake to reload cache files and so on. Number is in seconds, after which the |
| 248 | +# server will shut down. |
| 249 | +# |
| 250 | +#BB_SERVER_TIMEOUT = "60" |
| 251 | + |
| 252 | +# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to |
| 253 | +# track the version of this file when it was generated. This can safely be ignored if |
| 254 | +# this doesn't mean anything to you. |
| 255 | +CONF_VERSION = "2" |
| 256 | + |
| 257 | +# Set the root password to '0penBmc' |
| 258 | +# Defaults from meta-phosphor/conf/distro/include/phosphor-defaults.inc |
0 commit comments