documentation/ref-manual/faq.rst

9 **A:** The term ``Poky`` refers to the specific reference build
12 generic term used here for the build system is the "OpenEmbedded build
26 section for steps on how to update your build tools.
41    build and integration tests.
55 **Q:** Are there any products built using the OpenEmbedded build system?
59 OpenEmbedded build system. See the `Vernier
62 the OpenEmbedded build system and the Yocto Project team announces them
65 **Q:** What does the OpenEmbedded build system produce as output?
68 various formats, the output of an OpenEmbedded build depends on how you
82 **A:** The OpenEmbedded build system can build packages in various
92 **A:** You are probably running the build on an NTFS filesystem. Use
95 **Q:** I see lots of 404 responses for files when the OpenEmbedded build
98 **A:** Nothing is wrong. The OpenEmbedded build system checks any
100 The build system does this searching for both source archives and
104 into the build system. Consequently, if an upstream source disappears,
120 **A:** Most source fetching by the OpenEmbedded build system is done by
149 used for the build. These are usually tools that are needed to assist
150 the build in some way such as ``quilt-native``, which is used to apply
154 **Q:** I'm seeing random build failures. Help?!
156 **A:** If the same build is failing in totally different and random
159 -  The hardware you are running the build on has some problem.
161 -  You are running the build under virtualization, in which case the
164 The OpenEmbedded build system processes a massive amount of data that
169 **Q:** When I try to build a native recipe, the build fails with
182 the build again.
185 caused when the OpenEmbedded build system finds and uses previously
186 installed files during a native build. This type of issue might not be
233 **A:** By default, the OpenEmbedded build system creates images that are
237 -  *Image Size:* The OpenEmbedded build system uses the
239    the size of the image in Kbytes. The build system determines the size
246    to define the multiplier that the build system applies to the initial
251    variable to add additional free space to the image. The build system
258 of the tools the OpenEmbedded build system depends on, such as
270 OpenEmbedded build system to use its internally built toolchain (i.e.
282 **Q:** How does the OpenEmbedded build system obtain source code and
285 **A:** The way the build system obtains source code is highly
286 configurable. You can setup the build system to get source code in most
289 When the build system searches for source code, it first tries the local
294 Assuming your distribution is "poky", the OpenEmbedded build system uses
300 As an example, you could add a specific server for the build system to
310 These changes cause the build system to intercept Git, FTP, HTTP, and
328 limits the build system to pulling source from the :term:`PREMIRRORS` only.
336 statement tells the build system to generate mirror tarballs. This
338 however, the technique can simply waste time during the build.
351 These changes would cause the build system to successfully fetch source
355 The build system also honors the standard shell environment variables
365 **Q:** Can I get rid of build output so I can start over?
367 **A:** Yes - you can easily do this. When you use BitBake to build an
368 image, all the build output goes into the directory created when you run
369 the build environment setup script (i.e.
370 :ref:`structure-core-script`). By default, this :term:`Build Directory`
371 is named ``build`` but can be named
374 Within the Build Directory, is the ``tmp`` directory. To remove all the
375 build output yet preserve any source code or downloaded files from
389 mainstream Linux distributions as well as for the OpenEmbedded build
391 Autotools configuration scripts, and other build systems are expected to
396 variables when the build system actually installs the files. It is
400 When the OpenEmbedded build system uses a recipe to build a
403 system of that image. Thus, the build system provides a value of
407 Meanwhile, ``DESTDIR`` is a path within the :term:`Build Directory`.
409 native program (i.e. one that is intended to run on the build machine),
410 that program is never installed directly to the build machine's root
411 file system. Consequently, the build system uses paths within the Build
423    /home/maxtothemax/poky-bootchart2/build/tmp/work/i586-poky-linux/zlib/
426    /home/maxtothemax/poky-bootchart2/build/tmp/work/x86_64-linux/
428       build/tmp/sysroots/x86_64-linux/usr/bin
441 **A:** This situation results when a build system does not recognize the
449 environment variable. Check the build system to see if these kinds