| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | varlocality.rst | 28 - :term:`DISTRO`
30 - :term:`DISTRO_NAME`
32 - :term:`DISTRO_VERSION`
34 - :term:`MAINTAINER`
36 - :term:`PACKAGE_CLASSES`
38 - :term:`TARGET_OS`
40 - :term:`TARGET_FPU`
42 - :term:`TCMODE`
44 - :term:`TCLIBC`
53 - :term:`TARGET_ARCH`
[all …]
|
| H A D | variables.rst | 10 :term:`A <ABIEXTENSION>` :term:`B` :term:`C <CACHE>`
11 :term:`D` :term:`E <EFI_PROVIDER>` :term:`F <FAKEROOT>`
12 :term:`G <GCCPIE>` :term:`H <HGDIR>` :term:`I <ICECC_CLASS_DISABLE>`
13 :term
[all...] |
| H A D | terms.rst | 13 :term:`Append Files`
52 :term:`BitBake`
57 :term:`Board Support Package (BSP)`
62 :term:`Build Directory`
63 This term refers to the area used by the OpenEmbedded build system for
67 :term:`TOPDIR` variable points to the :term:`Build Directory`.
69 You have a lot of flexibility when creating the :term:`Build Directory`.
71 examples assume your :term:`Source Directory` is named ``poky``:
73 - Create the :term:`Build Directory` inside your Source Directory and let
74 the name of the :term:`Build Directory` default to ``build``:
[all …]
|
| H A D | classes.rst | 14 Any :term:`Metadata` usually found in a recipe can also be
17 beneath the ``meta*/`` directory found in the :term:`Source Directory`:
25 :term:`BUILDDIR` (e.g. ``build/``) in the same way as
27 in :term:`BBPATH` using the same method by which ``.conf``
50 :term:`RDEPENDS` and
51 :term:`TUNE_PKGARCH` variables, should never be
59 different :term:`MACHINE` is built even when the recipe never changes.
79 the :term:`ARCHIVER_MODE` variable for information
105 the same as the :ref:`ref-classes-autotools` class but builds with :term:`B`
106 == :term
[all...] |
| H A D | qa-checks.rst | 62 :term:`TMPDIR`, which are incorrect for the target and
90 corresponding entry in :term:`RDEPENDS`. If
91 particular files are required at runtime then :term:`RDEPENDS` should be
104 :term:`RDEPENDS` value being added at the packaging
107 to add an explicit :term:`RDEPENDS` for the dependency.
117 :term:`FILES` (and possibly
118 :term:`PACKAGES`) such that the specified ``.so``
127 Change :term:`FILES` (and possibly
128 :term:`PACKAGES`) such that the specified ``.a`` file
142 :term:`INSANE_SKIP` for the package.
[all …]
|
| /openbmc/phosphor-webui/app/common/directives/ |
| H A D | vt100plus.js | 51 function customVT100PlusKey(ev, term) { argument
62 term.handler(EscapeSequences.C0.BS); // Backspace
64 term.handler(EscapeSequences.C0.DEL); // Delete
68 term.handler(EscapeSequences.C0.ESC + '?');
71 term.handler(EscapeSequences.C0.ESC + '/');
74 term.handler(EscapeSequences.C0.ESC + 'k');
77 term.handler(EscapeSequences.C0.ESC + 'h');
80 term.handler(EscapeSequences.C0.ESC + '+');
83 term.handler(EscapeSequences.C0.ESC + '-');
86 term.handler(EscapeSequences.C0.ESC + '1');
[all …]
|
| H A D | serial-console.js | 17 function measureChar(term) { argument
25 fontFamily = term.getOption('fontFamily');
26 fontSize = term.getOption('fontSize');
143 var term = new Terminal();
150 term.open(terminal);
151 term.fit();
153 term.attachCustomKeyEventHandler(customKeyHandlers); field in AnonymousFunctiond2c7d9910300.AnonymousClassd2c7d9910501
160 term.setOption('theme', SOL_THEME);
166 term.attach(ws);
183 term.fit();
[all …]
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 22 - System resources, like disk space to be used (:term:`BB_DISKMON_DIRS`),
23 or the number of tasks to be run in parallel by BitBake (:term:`BB_NUMBER_THREADS`).
25 - How the fetchers shall behave, e.g., :term:`BB_FETCH_PREMIRRORONLY` is used
27 :term:`PREMIRRORS` for files.
36 - Like :term:`B` or :term:`T`, that are used to specify directories used by
38 specified in ``bitbake.conf``. Some, like :term:`B`, are quite often
46 data reuse between build runs like :term:`CACHE`, :term:`DL_DIR` or
47 :term:`PERSISTENT_DIR`. Those are usually global.
57 - :term:`LAYERDEPENDS` is used to configure on which layers a given layer
60 - The configured layers are contained in :term:`BBLAYERS` and files in
[all …]
|
| H A D | bitbake-user-manual-ref-variables.rst | 29 :term:`ASSUME_PROVIDED`
30 Lists recipe names (:term:`PN` values) BitBake does not
34 In OpenEmbedded-Core, :term:`ASSUME_PROVIDED` mostly specifies native
39 :term:`AZ_SAS`
51 :term:`B`
55 :term:`BB_ALLOWED_NETWORKS`
61 :term:`BB_NO_NETWORK` is either not set or
86 Using :term:`BB_ALLOWED_NETWORKS` in conjunction with
87 :term:`PREMIRRORS` is very useful. Adding the
88 host you want to use to :term
[all...] |
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | temporary-source-code.rst | 11 :term:`Build Directory`, and then you can force a re-compile and quickly
16 build packages is available in the :term:`Build Directory` as defined by the
17 :term:`S` variable. Below is the default value for the :term:`S` variable as
19 :term:`Source Directory`::
24 :term:`S` variable when the default isn't accurate.
28 The :term:`BP` represents the base recipe name, which consists of the name
38 (:term:`UNPACKDIR`) is defined as follows::
43 (:term:`WORKDIR`) is defined as
50 - :term
[all...] |
| H A D | sbom.rst | 16 (:term:`SBOM`), using the :term:`SPDX` standard.
20 :term:`SBOM` tooling is often used to ensure open source license compliance by
24 :term:`SBOM` information is also critical to performing vulnerability exposure
28 though the :term:`Poky` reference distribution has it enabled out of the box.
35 In the :term:`Poky` reference distribution, :term:`SPDX` generation does
37 :term:`configuration file`::
43 - :term:`SPDX` output in JSON format as an ``IMAGE-MACHINE.spdx.json`` file in
44 ``tmp/deploy/images/MACHINE/`` inside the :term
[all...] |
| H A D | multiconfig.rst | 10 section uses that term throughout.
20 target's configuration separately using a parallel :term:`configuration file` in
21 the :term:`Build Directory` or configuration directory within a layer, and you
28 :term:`Configuration File` for each build target (each multiconfig).
30 each configuration file will define the :term:`MACHINE` and the
31 temporary directory (:term:`TMPDIR`) BitBake uses for the build.
35 Whether the same temporary directory (:term:`TMPDIR`) can be shared will
37 configurations. Multiple :term:`MACHINE` targets can share the same
38 :term:`TMPDIR` as long as the rest of the configuration is the same,
39 multiple :term:`DISTRO` settings would need separate :term:`TMPDIR`
[all …]
|
| H A D | building.rst | 23 :term:`Toaster`, see the
40 places it in your :term:`Build Directory` under ``tmp/deploy/images``. For
61 uses ``build`` as the default :term:`Build Directory` in your current work
63 specify a different :term:`Build Directory`.
67 A common practice is to use a different :term:`Build Directory` for
70 event, it's typically cleaner to locate the :term:`Build Directory`
75 :term:`Build Directory`, is set up how you want it. This file defines many
77 through the :term:`MACHINE` variable, the packaging format used during
78 the build (:term:`PACKAGE_CLASSES`), and a centralized tarball download
79 directory through the :term
[all...] |
| H A D | customizing-images.rst | 21 the :term:`IMAGE_INSTALL` variable with the ``:append`` operator::
46 :term:`CORE_IMAGE_EXTRA_INSTALL` variable. If you use this variable, only
54 :term:`IMAGE_FEATURES` and
55 :term:`EXTRA_IMAGE_FEATURES`
57 equivalent, best practices dictate using :term:`IMAGE_FEATURES` from within
58 a recipe and using :term:`EXTRA_IMAGE_FEATURES` from within your
59 ``local.conf`` file, which is found in the :term:`Build Directory`.
64 :term:`IMAGE_FEATURES` of which most map to package groups while some, such
67 In summary, the file looks at the contents of the :term:`IMAGE_FEATURES`
71 :term:`IMAGE_INSTALL` variable.
[all …]
|
| /openbmc/u-boot/tools/buildman/ |
| H A D | board.py | 217 for term in word.split('&'):
218 if term:
219 sym_build.append(term)
223 term = None
229 term.AddExpr(sym)
232 if term:
233 terms.append(term)
234 term = Term()
235 term.AddExpr(sym)
236 if term:
[all …]
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-5.1.rst | 14 :term:`WORKDIR` changes
20 If a recipe has :term:`S` set to be :term:`WORKDIR`, this is no longer
25 Any :term:`WORKDIR` references where files from :term:`SRC_URI` are referenced
26 should be changed to :term:`S`. These are commonly in :ref:`ref-tasks-compile`,
27 :ref:`ref-tasks-compile`, :ref:`ref-tasks-install` and :term:`LIC_FILES_CHKSUM`.
29 :term:`WORKDIR` references in recipes
32 :term:`WORKDIR` references in other recipes need auditing. If they reference
33 files from :term
[all...] |
| H A D | migration-1.4.rst | 23 :term:`RDEPENDS`,
24 :term:`RRECOMMENDS`,
25 :term:`RSUGGESTS`,
26 :term:`RPROVIDES`,
27 :term:`RCONFLICTS`,
28 :term:`RREPLACES`, :term:`FILES`,
29 :term:`ALLOW_EMPTY`, and the pre, post, install,
33 instead of :term:`RDEPENDS`. BitBake uses more strict checks when it
55 :term:`SRC_URI`, the build system now uses
56 :term:`FILESOVERRIDES` instead of
[all …]
|
| H A D | migration-4.0.rst | 28 - ``BB_ENV_WHITELIST`` became :term:`BB_ENV_PASSTHROUGH`
29 - ``BB_ENV_EXTRAWHITE`` became :term:`BB_ENV_PASSTHROUGH_ADDITIONS`
30 - ``BB_HASHBASE_WHITELIST`` became :term:`BB_BASEHASH_IGNORE_VARS`
31 - ``BB_HASHCONFIG_WHITELIST`` became :term:`BB_HASHCONFIG_IGNORE_VARS`
34 - ``CVE_CHECK_PN_WHITELIST`` became :term:`CVE_CHECK_SKIP_RECIPE`
35 - ``CVE_CHECK_WHITELIST`` became :term:`CVE_CHECK_IGNORE`
36 - ``ICECC_USER_CLASS_BL`` became :term:`ICECC_CLASS_DISABLE`
37 - ``ICECC_SYSTEM_CLASS_BL`` became :term:`ICECC_CLASS_DISABLE`
38 - ``ICECC_USER_PACKAGE_WL`` became :term:`ICECC_RECIPE_ENABLE`
39 - ``ICECC_USER_PACKAGE_BL`` became :term:`ICECC_RECIPE_DISABLE`
[all …]
|
| H A D | migration-4.1.rst | 19 be installed on the build host. A new :term:`buildtools-make` tarball has been
22 :term:`buildtools` tarball. For more information see
32 building an SDK, or if you have added ``dev-deps`` to :term:`IMAGE_FEATURES`),
33 recommends (as defined by :term:`RRECOMMENDS`) are no longer installed.
37 you can explicitly install items by adding them to :term:`IMAGE_INSTALL` in
38 image recipes or :term:`TOOLCHAIN_TARGET_TASK` for the SDK.
46 The default for ``${PN}-dev`` package is now to use :term:`RRECOMMENDS` instead
47 of :term:`RDEPENDS` to pull in the main package. This takes advantage of a
48 change to complimentary package installation to not follow :term:`RRECOMMENDS`
68 A. Use ``dropbear`` in :term:`IMAGE_INSTALL` instead of
[all …]
|
| H A D | migration-4.3.rst | 17 The :term:`OLDEST_KERNEL` setting has been changed to "5.15" in this release, meaning that
35 :term:`FILE_LAYERNAME` variable and the ``layer-<layername> override``. This is being used
114 - :term:`CVE_CHECK_IGNORE`: use :term:`CVE_STATUS` instead.
128 consoles listed in :term:`SERIAL_CONSOLES` are checked for their existence
138 - ``apmd``: obsolete (``apm`` in :term:`MACHINE_FEATURES` also removed).
165 - :term:`IMAGE_NAME` and :term:`IMAGE_LINK_NAME` now include the
166 :term:`IMAGE_NAME_SUFFIX` value directly. In practical terms, this means
169 :term:`IMAGE_NAME_SUFFIX` to "" and this will now be consistently respected
176 - :term:`SDK_NAME` now includes the values of :term:`IMAGE_BASENAME` and
177 :term:`MACHINE` so that they are unique when building SDKs for different
[all …]
|
| H A D | migration-1.5.rst | 69 - ``${``\ :term:`P`\ ``}`` and
70 ``${``\ :term:`PF`\ ``}`` are no longer added to
71 :term:`PROVIDES` by default in ``bitbake.conf``.
72 These version-specific :term:`PROVIDES` items were seldom used.
84 - If you have customized :term:`ERROR_QA` or
85 :term:`WARN_QA` values in your configuration, check
88 item not mentioned in :term:`ERROR_QA` or :term:`WARN_QA` would be treated as
90 the default value of :term:`WARN_QA`. All of the possible QA checks are
100 Thus, if you have customized your :term:`ERROR_QA` or :term:`WARN_QA` values
114 and tuning architecture through the :term:`SDK_NAME`
[all …]
|
| H A D | migration-5.2.rst | 17 ``debug-tweaks`` removed from :term:`IMAGE_FEATURES`
25 should be manually added to the :term:`IMAGE_FEATURES` variable. These are:
42 The :term:`OLDEST_KERNEL` setting is 5.15 in this release, meaning that
69 :term:`CARGO_INSTALL_LIBRARIES` variable.
80 :term:`PACKAGECONFIG` option as it is now implied by default.
85 the other service files were automatically added to the :term:`FILES` variable of
95 ``b.service`` was explicitly added to package ``B`` using :term:`FILES` and
96 :term:`SYSTEMD_SERVICE` variables.
100 Now all service files must be explicitly added to :term:`FILES`.
107 - If ``pni-names`` is not in the :term:`DISTRO_FEATURES`, the `Predictable
[all …]
|
| H A D | migration-1.6.rst | 47 The following changes have been made to :term:`BitBake`.
55 :term:`SRC_URI`, BitBake will now validate the
56 :term:`SRCREV` value against the branch. You can specify
65 you can add ";nobranch=1" to the end of the URL within :term:`SRC_URI`.
136 :term:`TMPDIR` can no longer be on an NFS mount. NFS does
138 unexpected issues if used to store :term:`TMPDIR`.
140 The check for this occurs on startup. If :term:`TMPDIR` is detected on an
149 detected during a build. For :term:`PR` increments on changes,
159 The "sum.jffs2" option for :term:`IMAGE_TYPES` has
168 The :term:`COPY_LIC_MANIFEST` variable must now
[all …]
|
| /openbmc/openbmc/poky/documentation/contributor-guide/ |
| H A D | recipe-style-guide.rst | 16 and the recipe would set :term:`PV`.
22 or in BitBake variable terms ${:term:`PE`}:${:term:`PV`}-${:term:`PR`}. We
26 In most cases the version :term:`PV` will be set automatically from the recipe
38 may be found where :term:`PV` is set as a combination of the prior version
49 version of software (e.g. is not a tagged version), the :term:`PV` variable
50 should include the sign ``+``, so :term:`bitbake` automatically includes package
58 also useful when using :term:`AUTOREV` to set the recipe to increment source
64 The :term:`PR` variable is used to indicate different revisions of a recipe
70 When :term:`PV` increases, any existing :term:`PR` value can and should be
73 If :term:`PV` changes in such a way that it does not increase with respect to
[all …]
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 27 specific to the :term:`Build Host`.
30 :term:`ESDK_LOCALCONF_REMOVE`
38 :term:`ESDK_LOCALCONF_REMOVE`
42 :term:`ESDK_LOCALCONF_ALLOW`
44 :term:`ESDK_LOCALCONF_ALLOW` overrides either of the previous two
47 - Classes inherited globally with :term:`INHERIT` that are listed in
48 :term:`ESDK_CLASS_INHERIT_DISABLE` are disabled. Using
49 :term:`ESDK_CLASS_INHERIT_DISABLE` to disable these classes is the typical
63 In most cases, the extensible SDK defaults should work with your :term:`Build
68 :term:`INHERIT` variable and you
[all …]
|