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