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