Lines Matching refs:term
14 Any :term:`Metadata` usually found in a recipe can also be
17 the ``meta*/`` directory found in the :term:`Source Directory`.
19 :term:`BUILDDIR` (e.g. ``build/``) in the same way as
21 in :term:`BBPATH` using the same method by which ``.conf``
44 :term:`RDEPENDS` and
45 :term:`TUNE_PKGARCH` variables, should never be
53 different :term:`MACHINE` is built even when the recipe never changes.
73 the :term:`ARCHIVER_MODE` variable for information
98 the same as the ``autotools`` class but builds with :term:`B`
99 == :term:`S`. This method is useful when out-of-tree build
113 additional parameters to ``configure`` through the :term:`EXTRA_OECONF`
114 or :term:`PACKAGECONFIG_CONFARGS`
119 additional arguments through the :term:`EXTRA_OEMAKE` variable.
122 passes in ``${``\ :term:`D`\ ``}`` as ``DESTDIR``.
140 :term:`EXTRA_OEMAKE` variable as well as the
171 :term:`S`::
195 :term:`BINCONFIG_GLOB` variable for more
207 :term:`BINCONFIG` variable within the recipe inheriting
231 :term:`BUILDSTATS_BASE` directory, which defaults
238 :term:`USER_CLASSES` variable from your
241 remove "buildstats" from the :term:`USER_CLASSES` list.
286 the :term:`EXTRA_OECMAKE` variable to specify
312 :term:`DOC_COMPRESS` variable.
341 :term:`IMAGE_FEATURES`.
370 automatically creating :term:`SPDX` :term:`SBOM` documents based upon image
377 The toplevel :term:`SPDX` output file is generated in JSON format as a
379 :term:`Build Directory`. There are other related files in the same directory,
383 by the :term:`SPDX_PRETTY`, :term:`SPDX_ARCHIVE_PACKAGED`,
384 :term:`SPDX_ARCHIVE_SOURCES` and :term:`SPDX_INCLUDE_SOURCES` variables.
449 ``CVE-ID.patch``, e.g. ``CVE-2019-20633.patch``, in the :term:`SRC_URI` and using
452 If the recipe lists the ``CVE-ID`` in :term:`CVE_CHECK_IGNORE` variable, then the CVE state is repo…
458 fixed in recipes by adjusting the CVE product name using :term:`CVE_PRODUCT` and :term:`CVE_VERSION…
459 :term:`CVE_PRODUCT` defaults to the plain recipe name :term:`BPN` which can be adjusted to one or m…
465 if the default recipe version :term:`PV` does not match the version numbers of the software compone…
466 in upstream releases or the CVE database, then the :term:`CVE_VERSION` variable can be used to set …
495 of ``.so`` type), use the :term:`LEAD_SONAME`
505 :term:`DEPLOY_DIR_IMAGE` directory. The main
509 deployed to :term:`DEPLOYDIR`, and use ``addtask`` to
513 staging the files from :term:`DEPLOYDIR` to :term:`DEPLOY_DIR_IMAGE`.
531 :term:`BBCLASSEXTEND` to add a variant of the
540 :term:`DEFAULT_PREFERENCE` set to "-1".
554 The :term:`BBCLASSEXTEND` syntax (i.e. ``devupstream:target``) provides
572 By default, the OpenEmbedded build system uses the :term:`S`
573 and :term:`B` variables to locate unpacked recipe source code
576 :term:`EXTERNALSRC` and
577 :term:`EXTERNALSRC_BUILD` variables to
578 ultimately define :term:`S` and :term:`B`.
581 that use the :term:`B` variable to point to the directory in
583 from the recipes. By default, the :term:`B` directory is set to the
584 following, which is separate from the source directory (:term:`S`)::
589 :term:`WORKDIR`, :term:`BPN`, and
590 :term:`PV`,
593 ``meta/classes/externalsrc.bbclass`` in the :term:`Source Directory`.
608 :term:`EXTRA_USERS_PARAMS` variable.
668 :term:`DISTRO_FEATURES`, :term:`MACHINE_FEATURES` or :term:`COMBINED_FEATURES`.
672 - :term:`REQUIRED_DISTRO_FEATURES`
673 - :term:`CONFLICT_DISTRO_FEATURES`
674 - :term:`ANY_OF_DISTRO_FEATURES`
700 package, set :term:`FONT_PACKAGES` to specify the
709 ``${``\ :term:`ROOTFS`\ ``}``, which must have been built
720 package (``${``\ :term:`PN`\ ``}-gconf``) that is created
742 :term:`SRC_URI` to download the source from the GNOME
743 mirrors as well as extending :term:`FILES` with the typical
754 :term:`DISTRO_FEATURES` as well as
756 :term:`MACHINE_FEATURES`.
761 should be disabled through :term:`DISTRO_FEATURES_BACKFILL_CONSIDERED` or
762 :term:`MACHINE_FEATURES_BACKFILL_CONSIDERED`, respectively.
774 - :term:`INITRD`: Indicates list of filesystem images to
777 - :term:`ROOTFS`: Indicates a filesystem image to include
780 - :term:`GRUB_GFXSERIAL`: Set this to "1" to have
783 - :term:`LABELS`: A list of targets for the automatic
786 - :term:`APPEND`: An override list of append strings for
789 - :term:`GRUB_OPTS`: Additional options to add to the
793 - :term:`GRUB_TIMEOUT`: Timeout before executing
843 :term:`GTKIMMODULES_PACKAGES` to specify
881 If :term:`ICECC_PATH` is not set in your
883 using ``which``. If :term:`ICECC_ENV_EXEC` is set
897 :term:`ICECC_RECIPE_DISABLE` and
898 :term:`ICECC_CLASS_DISABLE` variables,
903 :term:`ICECC_RECIPE_ENABLE` variable in
905 using an empty :term:`PARALLEL_MAKE` variable.
909 populates :term:`SSTATE_MIRRORS` and they want to
910 reuse sstate from :term:`SSTATE_MIRRORS`, then all developers and the build
916 :term:`ICECC_DISABLED` variable to "1" as follows::
938 - The :term:`IMAGE_FSTYPES` variable controls the types of images to
941 - The :term:`IMAGE_INSTALL` variable controls the list of packages to
966 :term:`IMAGE_FSTYPES` variable. You can use this
988 :term:`IMAGE_FSTYPES`. This would also be similar for Virtual Box Virtual Disk
998 specified by :term:`EFI_PROVIDER` if
999 :term:`MACHINE_FEATURES` contains "efi".
1002 :term:`IMAGE_FSTYPES`.
1022 Use the :term:`WARN_QA` and
1023 :term:`ERROR_QA` variables to control the behavior of
1026 should use :term:`INSANE_SKIP`. For example, to skip
1037 Here are the tests you can list with the :term:`WARN_QA` and
1038 :term:`ERROR_QA` variables:
1059 specified through :term:`DEPENDS`, explicit
1060 :term:`RDEPENDS`, or task-level dependencies exists
1073 :term:`RDEPENDS` for the package in question on ``initscripts-functions``
1093 :term:`RDEPENDS`,
1094 :term:`RRECOMMENDS`,
1095 :term:`RSUGGESTS`,
1096 :term:`RPROVIDES`,
1097 :term:`RREPLACES`, and
1098 :term:`RCONFLICTS` variable values). Any invalid
1120 :term:`QA_EMPTY_DIRS` variable.
1132 :term:`RDEPENDS` exist to handle any file-level
1135 - ``files-invalid:`` Checks for :term:`FILES` variable
1148 :term:`INCOMPATIBLE_LICENSE`.
1157 way of the :term:`FILES` variable. Files that do not
1164 :term:`DESCRIPTION`,
1165 :term:`SUMMARY`, :term:`LICENSE`, and
1166 :term:`SECTION` do not contain non-UTF-8 characters.
1170 being added to :term:`PACKAGECONFIG`. For
1175 - ``la:`` Checks ``.la`` files for any :term:`TMPDIR` paths. Any ``.la``
1180 :term:`LDFLAGS` options provided by the build system.
1181 If this test fails, check that the :term:`LDFLAGS` variable is being
1195 multiple times through the :term:`PACKAGES` variable
1211 :term:`TMPDIR`/:term:`WORKDIR` paths.
1217 :term:`PACKAGES` have names that do not contain
1221 - ``pkgv-undefined:`` Checks to see if the :term:`PKGV` variable is
1225 :term:`RDEPENDS`,
1226 :term:`RRECOMMENDS`,
1227 :term:`RSUGGESTS`,
1228 :term:`RCONFLICTS`,
1229 :term:`RPROVIDES`,
1230 :term:`RREPLACES`, :term:`FILES`,
1231 :term:`ALLOW_EMPTY`, ``pkg_preinst``,
1239 (:term:`PN`) value that appears in
1240 :term:`OVERRIDES`. If a recipe is named such that
1241 its :term:`PN` value matches something already in :term:`OVERRIDES` (e.g.
1242 :term:`PN` happens to be the same as :term:`MACHINE` or
1243 :term:`DISTRO`), it can have unexpected consequences.
1248 system paths such as :term:`TMPDIR`. If this test fails, bad ``-rpath``
1259 into :term:`TMPDIR` on the host. Such symlinks will
1270 in ``LICENSE:*`` should appear in :term:`LICENSE`).
1278 (i.e. :term:`WORKDIR`,
1279 :term:`DEPLOY_DIR`, :term:`D`,
1280 :term:`PN`, and :term:`PKGD`) are undefined
1321 :term:`STAGING_KERNEL_DIR` directory to allow out-of-tree module builds
1372 To create a FIT image, it is required that :term:`KERNEL_CLASSES`
1373 is set to include "kernel-fitimage" and :term:`KERNEL_IMAGETYPE`
1378 :term:`UBOOT_MKIMAGE_DTCOPTS` variable.
1383 specified by :term:`UBOOT_LOADADDRESS` and the entrypoint by
1384 :term:`UBOOT_ENTRYPOINT`.
1389 specified by :term:`UBOOT_DTBO_LOADADDRESS` for device tree overlays
1390 and by :term:`UBOOT_DTB_LOADADDRESS` for device tree binaries.
1395 is specified by :term:`UBOOT_RD_LOADADDRESS` and the entrypoint by
1396 :term:`UBOOT_RD_ENTRYPOINT`. The ramdisk is added to FIT image when
1397 :term:`INITRAMFS_IMAGE` is specified and that :term:`INITRAMFS_IMAGE_BUNDLE`
1403 in the same binary (example: zImage-initramfs-:term:`MACHINE`.bin).
1405 The Initramfs bundle can be enabled when :term:`INITRAMFS_IMAGE`
1406 is specified and that :term:`INITRAMFS_IMAGE_BUNDLE` is set to 1.
1408 by :term:`UBOOT_LOADADDRESS` and the entrypoint by :term:`UBOOT_ENTRYPOINT`.
1420 variables :term:`UBOOT_SIGN_ENABLE`, :term:`UBOOT_MKIMAGE_DTCOPTS`,
1421 :term:`UBOOT_SIGN_KEYDIR` and :term:`UBOOT_SIGN_KEYNAME` are set
1422 appropriately. The default values used for :term:`FIT_HASH_ALG` and
1423 :term:`FIT_SIGN_ALG` in ``kernel-fitimage`` are "sha256" and
1425 the ``kernel-fitimage`` class when both :term:`FIT_GENERATE_KEYS` and
1426 :term:`UBOOT_SIGN_ENABLE` are set to "1".
1484 added to a separate ``${``\ :term:`PN`\ ``}-bin`` package to
1507 the :term:`INHERIT_DISTRO` variable.
1577 :term:`MIRRORS` entries for source code mirrors. These
1579 in :term:`SRC_URI` within recipes is unavailable.
1631 build tools to run on the :term:`Build Host` (i.e. tools that use the compiler
1674 :term:`SDKMACHINE`).
1739 ``meta/classes`` in the :term:`Source Directory`.
1827 …This class must not be inherited directly. Use :term:`IMAGE_FEATURES` or :term:`EXTRA_IMAGE_FEATUR…
1862 :term:`PREMIRRORS` from which to first fetch source
1864 :term:`SRC_URI` within each recipe.
1867 :term:`SOURCE_MIRROR_URL`. Here is an example::
1873 in :term:`SOURCE_MIRROR_URL`.
1897 :term:`PACKAGE_CLASSES` variable defined in your ``conf/local.conf``
1898 configuration file, which is located in the :term:`Build Directory`.
1917 creates and processes more :term:`Metadata` than the IPK package
1918 manager. Consequently, you might consider setting :term:`PACKAGE_CLASSES` to
1950 ``${``\ :term:`DEPLOY_DIR_DEB`\ ``}`` directory.
1953 is enabled through the :term:`PACKAGE_CLASSES`
1964 ``${``\ :term:`DEPLOY_DIR_IPK`\ ``}`` directory.
1967 is enabled through the :term:`PACKAGE_CLASSES`
1978 ``${``\ :term:`DEPLOY_DIR_RPM`\ ``}`` directory.
1981 is enabled through the :term:`PACKAGE_CLASSES`
1991 ``${``\ :term:`DEPLOY_DIR_TAR`\ ``}`` directory.
1994 is enabled through the :term:`PACKAGE_CLASSES`
2000 :term:`PACKAGE_CLASSES` variable. You must use ``.deb``, ``.ipk``, or ``.rpm``
2009 ``pkgdata`` files found in :term:`PKGDATA_DIR`. These
2022 group recipes (e.g. :term:`PACKAGES`, :term:`PACKAGE_ARCH`, :term:`ALLOW_EMPTY`, and
2059 By default it determines the PyPI package name based upon :term:`BPN`
2062 :term:`PYPI_PACKAGE`.
2064 Variables set by the :ref:`pypi <ref-classes-pypi>` class include :term:`SRC_URI`, :term:`SECTION`,
2065 :term:`HOMEPAGE`, :term:`UPSTREAM_CHECK_URI`, :term:`UPSTREAM_CHECK_REGEX`
2066 and :term:`CVE_PRODUCT`.
2093 :term:`PEP517_BUILD_API` to the Python class which implements the PEP-517 build
2126 :term:`PIXBUF_PACKAGES` to specify the packages
2180 :term:`IMAGE_PKGTYPE`.
2185 ``${``\ :term:`SDK_ARCH`\ ``}-nativesdk``, which
2188 usage. These two images reside in :term:`SDK_OUTPUT`,
2218 :term:`PR` values.
2231 :term:`PR` values.
2245 automatically manage the incrementing of the :term:`PR`
2251 :term:`PRSERV_HOST` has been set.
2263 :term:`DISTRO_FEATURES`. See the
2372 ``${``\ :term:`LOG_DIR`\ ``}/error-report``.
2390 your ``local.conf`` file, which is found in the :term:`Build Directory`.
2400 or recipes you are working on to the :term:`RM_WORK_EXCLUDE` variable, which
2430 :term:`PACKAGE_CLASSES` variable.
2455 :term:`EXTRA_OESCONS` variable to specify
2576 data relevant to the current build in the :term:`CONFIG_SITE` variable that
2579 The class also provides variables like :term:`SITEINFO_ENDIANNESS` and
2580 :term:`SITEINFO_BITS` that can be used elsewhere in the metadata.
2589 :term:`INHERIT_DISTRO` variable's default value.
2611 :term:`WORKDIR`).
2620 ``${``\ :term:`D`\ ``}``. The ``do_populate_sysroot`` task
2623 :term:`SYSROOT_DIRS`,
2624 :term:`SYSROOT_DIRS_NATIVE`, and
2625 :term:`SYSROOT_DIRS_IGNORE`
2631 declaring a processing function in the :term:`SYSROOT_PREPROCESS_FUNCS`
2642 controlled by the :term:`SSTATE_SCAN_FILES`
2647 through the :term:`DEPENDS` variable. The recipe will
2652 :term:`WORKDIR`). The OpenEmbedded build system
2673 Because recipes can have other dependencies outside of :term:`DEPENDS`
2677 :term:`DEPENDS` but operate similarly.
2705 - :term:`INITRD`: Indicates list of filesystem images to
2709 - :term:`ROOTFS`: Indicates a filesystem image to include
2712 - :term:`AUTO_SYSLINUXMENU`: Enables creating
2715 - :term:`LABELS`: Lists targets for automatic
2718 - :term:`APPEND`: Lists append string overrides for each
2721 - :term:`SYSLINUX_OPTS`: Lists additional options
2725 - :term:`SYSLINUX_SPLASH`: Lists a background
2728 - :term:`SYSLINUX_DEFAULT_CONSOLE`: Set
2731 - :term:`SYSLINUX_SERIAL`: Sets an alternate
2735 - :term:`SYSLINUX_SERIAL_TTY`: Sets an
2747 in :term:`DISTRO_FEATURES`.
2752 ``${``\ :term:`D`\ ``}${systemd_unitdir}/system``. If the unit
2754 need to set :term:`SYSTEMD_PACKAGES` in your
2757 You should set :term:`SYSTEMD_SERVICE` to the
2760 the recipe's main package, use ``${``\ :term:`PN`\ ``}``. Here
2767 :term:`SYSTEMD_AUTO_ENABLE` to "disable".
2787 Set the :term:`EFI_PROVIDER` variable to
2792 the :term:`SYSTEMD_BOOT_CFG`,
2793 :term:`SYSTEMD_BOOT_ENTRIES`, and
2794 :term:`SYSTEMD_BOOT_TIMEOUT` variables.
2806 The :term:`OE_TERMINAL` variable controls which
2812 :term:`PATCHRESOLVE` is set to "user", the
2829 Best practices include using :term:`IMAGE_CLASSES` rather than
2830 :term:`INHERIT` to inherit the ``testimage`` class for automated image
2843 :term:`TESTIMAGE_AUTO` must be set to "1").
2862 Best practices include using :term:`IMAGE_CLASSES` rather than
2863 :term:`INHERIT` to inherit the ``testsdk`` class for automated SDK
2881 you can remove "texinfo-native" from :term:`ASSUME_PROVIDED` and makeinfo
2882 from :term:`SANITY_REQUIRED_UTILITIES`.
2930 See the :term:`UBOOT_CONFIG` and :term:`UBOOT_MACHINE` variables for additional
2974 - :term:`ALTERNATIVE`
2976 - :term:`ALTERNATIVE_LINK_NAME`
2978 - :term:`ALTERNATIVE_TARGET`
2980 - :term:`ALTERNATIVE_PRIORITY`
3003 Three variables control this class: :term:`INITSCRIPT_PACKAGES`,
3004 :term:`INITSCRIPT_NAME` and :term:`INITSCRIPT_PARAMS`. See the variable links
3018 recipe in the :term:`Source Directory` provides a simple
3025 :term:`USERADD_PACKAGES`,
3026 :term:`USERADD_PARAM`,
3027 :term:`GROUPADD_PARAM`, and
3028 :term:`GROUPMEMS_PARAM` variables.
3043 :term:`BBPATH` for ``files/passwd`` and ``files/group``
3047 variables. See the :term:`USERADDEXTENSION`,
3048 :term:`USERADD_UID_TABLES`,
3049 :term:`USERADD_GID_TABLES`, and
3050 :term:`USERADD_ERROR_DYNAMIC` variables.
3057 or disable the class by setting the :term:`USERADDEXTENSION` variable. If you
3058 enable or disable the class in a configured system, :term:`TMPDIR` might
3059 contain incorrect ``uid`` and ``gid`` values. Deleting the :term:`TMPDIR`
3102 :term:`EXTRA_OECONF` or
3103 :term:`PACKAGECONFIG_CONFARGS` variables