diff options
Diffstat (limited to 'poky/documentation/ref-manual/faq.rst')
| -rw-r--r-- | poky/documentation/ref-manual/faq.rst | 41 |
1 files changed, 27 insertions, 14 deletions
diff --git a/poky/documentation/ref-manual/faq.rst b/poky/documentation/ref-manual/faq.rst index 2d2aaad0a..576863eec 100644 --- a/poky/documentation/ref-manual/faq.rst +++ b/poky/documentation/ref-manual/faq.rst @@ -1,10 +1,10 @@ -.. SPDX-License-Identifier: CC-BY-2.0-UK +.. SPDX-License-Identifier: CC-BY-SA-2.0-UK *** FAQ *** -**Q:** How does Poky differ from `OpenEmbedded <http://www.openembedded.org/>`__? +**Q:** How does Poky differ from :oe_home:`OpenEmbedded <>`? **A:** The term ``Poky`` refers to the specific reference build system that the Yocto Project provides. Poky is based on @@ -21,9 +21,9 @@ Can I still use the Yocto Project? **A:** You can get the required tools on your host development system a couple different ways (i.e. building a tarball or downloading a -tarball). See the "`Required Git, tar, Python and gcc -Versions <#required-git-tar-python-and-gcc-versions>`__" section for -steps on how to update your build tools. +tarball). See the +":ref:`ref-manual/ref-system-requirements:required git, tar, python and gcc versions`" +section for steps on how to update your build tools. **Q:** How can you claim Poky / OpenEmbedded-Core is stable? @@ -207,7 +207,7 @@ section in the Yocto Project Development Tasks Manual. **Q:** How do I disable the cursor on my touchscreen device? **A:** You need to create a form factor file as described in the -":ref:`bsp-filelayout-misc-recipes`" section in +":ref:`bsp-guide/bsp:miscellaneous bsp-specific recipe files`" section in the Yocto Project Board Support Packages (BSP) Developer's Guide. Set the ``HAVE_TOUCHSCREEN`` variable equal to one as follows: :: @@ -220,7 +220,7 @@ default? **A:** The default interfaces file provided by the netbase recipe does not automatically bring up network interfaces. Therefore, you will need to add a BSP-specific netbase that includes an interfaces file. See the -":ref:`bsp-filelayout-misc-recipes`" section in +":ref:`bsp-guide/bsp:miscellaneous bsp-specific recipe files`" section in the Yocto Project Board Support Packages (BSP) Developer's Guide for information on creating these types of miscellaneous recipe files. @@ -370,7 +370,7 @@ redirect requests through proxy servers. **A:** Yes - you can easily do this. When you use BitBake to build an image, all the build output goes into the directory created when you run the build environment setup script (i.e. -````` <#structure-core-script>`__). By default, this :term:`Build Directory` +:ref:`structure-core-script`). By default, this :term:`Build Directory` is named ``build`` but can be named anything you want. @@ -414,7 +414,14 @@ that program is never installed directly to the build machine's root file system. Consequently, the build system uses paths within the Build Directory for ``DESTDIR``, ``bindir`` and related variables. To better understand this, consider the following two paths where the first is -relatively normal and the second is not: :: +relatively normal and the second is not: + +.. note:: + + Due to these lengthy examples, the paths are artificially broken + across lines for readability. + +:: /home/maxtothemax/poky-bootchart2/build/tmp/work/i586-poky-linux/zlib/ 1.2.8-r0/sysroot-destdir/usr/bin @@ -423,11 +430,6 @@ relatively normal and the second is not: :: zlib-native/1.2.8-r0/sysroot-destdir/home/maxtothemax/poky-bootchart2/ build/tmp/sysroots/x86_64-linux/usr/bin -.. note:: - - Due to these lengthy examples, the paths are artificially broken - across lines for readability. - Even if the paths look unusual, they both are correct - the first for a target and the second for a native recipe. These paths are a consequence of the ``DESTDIR`` @@ -449,3 +451,14 @@ variant. For another example, permissions errors might be caused by a Makefile that ignores ``DESTDIR`` or uses a different name for that environment variable. Check the the build system to see if these kinds of issues exist. + +**Q:** I'm adding a binary in a recipe but it's different in the image, what is +changing it? + +**A:** The first most obvious change is the system stripping debug symbols from +it. Setting :term:`INHIBIT_PACKAGE_STRIP` to stop debug symbols being stripped and/or +:term:`INHIBIT_PACKAGE_DEBUG_SPLIT` to stop debug symbols being split into a separate +file will ensure the binary is unchanged. The other less obvious thing that can +happen is prelinking of the image. This is set by default in local.conf via +:term:`USER_CLASSES` which can contain 'image-prelink'. If you remove that, the +image will not be prelinked meaning the binaries would be unchanged. |