documentation/ref-manual/faq.rst

1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
11 :term:`OpenEmbedded-Core (OE-Core)` and :term:`BitBake`. Thus, the
14 OpenEmbedded, with changes always being merged to OE-Core or BitBake
25 ":ref:`ref-manual/system-requirements:required git, tar, python and gcc versions`"
28 **Q:** How can you claim Poky / OpenEmbedded-Core is stable?
32 -  The Yocto Project team keeps :term:`OpenEmbedded-Core (OE-Core)` small and
37 -  The Yocto Project team runs manual and automated tests using a small,
40 -  The Yocto Project uses an autobuilder, which provides continuous
48 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
50 :doc:`/bsp-guide/index`.
61 for more information. There are a number of pre-production devices using
76 ":ref:`dev-manual/common-tasks:writing a new recipe`"
89 '``chmod: XXXXX new permissions are r-xrwxrwx, not r-xr-xr-x``'. What is
101 pre-checked out versions of SCM-managed software. These checks help in
107 **Q:** I have machine-specific data in a package for one machine only
108 but the package is being marked as machine-specific in all cases, how do
112 but make sure the package is manually marked as machine-specific for the
140 ``meta-poky/conf/site.conf.sample`` file that shows how to configure CVS
146 **Q:** What's the difference between ``target`` and ``target-native``?
148 **A:** The ``*-native`` targets are designed to run on the system being
150 the build in some way such as ``quilt-native``, which is used to apply
151 patches. The non-native version is the one that runs on the target
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
166 single-bit failures in any of these areas. True random failures have
201 ":ref:`overview-manual/development-environment:licensing`"
204 ":ref:`dev-manual/common-tasks:maintaining open source license compliance during your product's lif…
210 ":ref:`bsp-guide/bsp:miscellaneous bsp-specific recipe files`" section in
221 to add a BSP-specific netbase that includes an interfaces file. See the
222 ":ref:`bsp-guide/bsp:miscellaneous bsp-specific recipe files`" section in
228    meta-MACHINE/recipes-bsp/netbase/netbase/MACHINE/interfaces
229    meta-MACHINE/recipes-bsp/netbase/netbase_5.0.bbappend
237 -  *Image Size:* The OpenEmbedded build system uses the
244 -  *Overhead:* Use the
249 -  *Additional Free Space:* Use the
266 controls which ``tcmode-*.inc`` file to include from the
271 ``tcmode-default.inc``). However, other patterns are accepted. In
272 particular, "external-\*" refers to external toolchains. One example is
274 the separate ``meta-sourcery`` layer at
275 https://github.com/MentorEmbedded/meta-sourcery/.
279 up any pre-built objects in the toolchain such as ``libgcc``,
295 the Yocto Project source :term:`PREMIRRORS` by default for SCM-based
297 of other mirrors including the Yocto Project source mirror if those
305        git://.*/.* &YOCTO_DL_URL;/mirror/sources/ \
306        ftp://.*/.* &YOCTO_DL_URL;/mirror/sources/ \
307        http://.*/.* &YOCTO_DL_URL;/mirror/sources/ \
308        https://.*/.* &YOCTO_DL_URL;/mirror/sources/"
311 HTTPS requests and direct them to the ``http://`` sources mirror. You
336 statement tells the build system to generate mirror tarballs. This
337 technique is useful if you want to create a mirror server. If not,
340 Finally, consider an example where you are behind an HTTP-only firewall.
345        git://.*/.* &YOCTO_DL_URL;/mirror/sources/ \
346        ftp://.*/.* &YOCTO_DL_URL;/mirror/sources/ \
347        http://.*/.* &YOCTO_DL_URL;/mirror/sources/ \
348        https://.*/.* &YOCTO_DL_URL;/mirror/sources/"
367 **A:** Yes - you can easily do this. When you use BitBake to build an
370 :ref:`structure-core-script`). By default, this :term:`Build Directory`
379 ``-native`` recipes?
390 system. As such, a well-established solution exists. Makefiles,
393 ``sysconfdir`` that indicate where executables, libraries, and data
401 target-architecture program (i.e. one that is intended for inclusion on
423    /home/maxtothemax/poky-bootchart2/build/tmp/work/i586-poky-linux/zlib/
424       1.2.8-r0/sysroot-destdir/usr/bin
426    /home/maxtothemax/poky-bootchart2/build/tmp/work/x86_64-linux/
427       zlib-native/1.2.8-r0/sysroot-destdir/home/maxtothemax/poky-bootchart2/
428       build/tmp/sysroots/x86_64-linux/usr/bin
431 they both are correct - the first for a target and the second for a
436 **Q:** The files provided by my ``*-native`` recipe do not appear to be
446 "/usr/bin" worked most of the time, but not for the recipe's ``-native``