meta-poky/conf/local.conf.sample

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
7 # can be placed in this file but new users likely won't need any of them
19 # of emulated machines available which can boot and run in the QEMU emulator:
44 # from various upstream projects. This can take a while, particularly if your network
46 # can preserve this directory to speed up this part of subsequent builds. This directory
57 # This is done using "shared state" files which can be thought of as cache objects
60 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
75 # which can use Gigabytes of hard disk space.
100 # can be enabled at once and the first item listed in the variable will be used
114 # you can build the SDK packages for architectures other than the machine you are
124 # variable can contain the following options:
140 # There are other application targets that can be used here too, see
149 # enable extra features. Some available options which can be included in this variable
157 # The build system can test booting virtual machine images under qemu (an emulator)
158 # after any root filesystems are created and run tests against those images. It can also
168 # can launch an interactive shell. It needs to do this since the build is
189 # of the build. The reason for this is that running completely out of space can corrupt
206 # As mentioned above, shared state files are prebuilt cache data objects which can be
207 # used to accelerate build time. This variable can be used to configure the system
210 # This can be a filesystem directory, or a remote url such as https or ftp. These
224 # The Yocto Project has prebuilt artefacts available for its releases, you can enable
228 # present in the cache. It assumes you can download something faster than you can build it
238 # By default native qemu will build with a builtin VNC server where graphical output can be
245 # You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
255 # artifact can be reused as equivalent, even if the current task hash doesn't
258 # A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
266 # Bitbake's server component can stay in memory after the UI for the current command
267 # has completed. This means subsequent commands can run faster since there is no need
274 # track the version of this file when it was generated. This can safely be ignored if