documentation/ref-manual/faq.rst

1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
13 ---------------------------------------
17 :term:`OpenEmbedded-Core (OE-Core)` and :term:`BitBake`. Thus, the
20 OpenEmbedded, with changes always being merged to OE-Core or BitBake
24 How can you claim Poky / OpenEmbedded-Core is stable?
25 -----------------------------------------------------
29 -  The Yocto Project team keeps :term:`OpenEmbedded-Core (OE-Core)` small and
31    available in other OpenEmbedded community layers. Keeping it small
34 -  The Yocto Project team runs manual and automated tests using a small,
37 -  The Yocto Project uses an :yocto_ab:`autobuilder <>`, which provides
41 -----------------------------------------------------------------
48 Why isn't systemd the default init system for OpenEmbedded-Core/Yocto Project or in Poky?
49 -----------------------------------------------------------------------------------------
56 or may not align with what the objectives and direction :term:`OpenEmbedded-Core
57 (OE-Core)` or Yocto Project want to take. It doesn't support all of our targets.
58 For example `musl <https://www.musl-libc.org/>`__ support in systemd is
66 Our automated testing includes it through the ``poky-altcfg`` :term:`DISTRO` and
74 -----------------------------------------------
79 tarball). See the ":ref:`ref-manual/system-requirements:required git, tar, python, make and gcc ver…
83 -----------------------------------------------------------------------------------------
86 configurable. You can setup the build system to get source code in most
95 the Yocto Project source :term:`PREMIRRORS` by default for SCM-based
139 Finally, consider an example where you are behind an HTTP-only firewall.
178 ``meta-poky/conf/templates/default/site.conf.sample`` file that shows
191 -----------------------------------
193 See the ":ref:`dev-manual/external-toolchain:optionally using an external toolchain`"
197 -------------------------------------
200 ``chmod: XXXXX new permissions are r-xrwxrwx, not r-xr-xr-x``,
206 --------------------------------------------------------------------
211 pre-checked out versions of SCM-managed software. These checks help in
217 -----------------------------------
222 -  The hardware you are running the build on has some problem.
224 -  You are running the build under virtualization, in which case the
229 single-bit failures in any of these areas. True random failures have
233 --------------------------------------------------
252 Why don't other recipes find the files provided by my ``*-native`` recipe?
253 --------------------------------------------------------------------------
257 could be getting permission errors during the :ref:`ref-tasks-install`
265 "/usr/bin" worked most of the time, but not for the recipe's ``-native``
272 --------------------------------------------------
274 Yes --- you can easily do this. When you use BitBake to build an
276 the build environment setup script (i.e.  :ref:`structure-core-script`).
285 ------------------------------------------------------------------------
295 encountered. This would lead to bizarre class interactions when new layers are
307 ----------------------------------------------------------
315 -------------------------------------------------
320 ":ref:`dev-manual/layers:understanding and creating layers`"
322 :doc:`/bsp-guide/index`.
328 ---------------------------------------------------
332 ":ref:`dev-manual/new-recipe:writing a new recipe`"
336 ----------------------------------------------
347 ":ref:`overview-manual/development-environment:licensing`"
349 ":ref:`dev-manual/licenses:maintaining open source license compliance during your product's lifecyc…
353 ---------------------------------------------------------------
362 ----------------------------------------------------------------
364 If you have machine-specific data in a package for one machine only
365 but the package is being marked as machine-specific in all cases,
367 However, but make sure the package is manually marked as machine-specific for the
369 is in the ``meta/classes-global/base.bbclass`` file.
371 What's the difference between ``target`` and ``target-native``?
372 ---------------------------------------------------------------
374 The ``*-native`` targets are designed to run on the system being
376 the build in some way such as ``quilt-native``, which is used to apply
377 patches. The non-native version is the one that runs on the target
380 Why do ``${bindir}`` and ``${libdir}`` have strange values for ``-native`` recipes?
381 -----------------------------------------------------------------------------------
392 system. As such, a well-established solution exists. Makefiles,
403 target-architecture program (i.e. one that is intended for inclusion on
418    /home/maxtothemax/poky-bootchart2/build/tmp/work/i586-poky-linux/zlib/
419       1.2.8-r0/sysroot-destdir/usr/bin
421    /home/maxtothemax/poky-bootchart2/build/tmp/work/x86_64-linux/
422       zlib-native/1.2.8-r0/sysroot-destdir/home/maxtothemax/poky-bootchart2/
423       build/tmp/sysroots/x86_64-linux/usr/bin
425 Even if the paths look unusual, they both are correct --- the first for
431 --------------------------------------------
437 -  *Image Size:* The OpenEmbedded build system uses the
444 -  *Overhead:* Use the
449 -  *Additional Free Space:* Use the
456 ------------------------------------------
464 ------------------------------------------------------------------
475 -----------------------------------------------------
478 ":ref:`bsp-guide/bsp:miscellaneous bsp-specific recipe files`" section in
485 ----------------------------------------------------
489 to add a BSP-specific netbase that includes an interfaces file. See the
490 ":ref:`bsp-guide/bsp:miscellaneous bsp-specific recipe files`" section in
496    meta-MACHINE/recipes-bsp/netbase/netbase/MACHINE/interfaces
497    meta-MACHINE/recipes-bsp/netbase/netbase_5.0.bbappend