| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | bin_package.bbclass | 9 # * The files have been unpacked to ${S} by base.bbclass 19 # Then the files would be unpacked to ${WORKDIR}/foo-1.0, otherwise
|
| H A D | image.bbclass | 329 # The functions should use ${IMAGE_ROOTFS} to find the unpacked rootfs
|
| /openbmc/openbmc/poky/meta/recipes-core/ovmf/ |
| H A D | ovmf-shell-image.bb | 14 # We want a minimal image with just ovmf-shell-efi unpacked in it. We
|
| /openbmc/openbmc/poky/meta/recipes-support/vim/files/ |
| H A D | no-path-adjust.patch | 33 # install the language specific files for tools, if they were unpacked
|
| /openbmc/docs/architecture/ |
| H A D | ipmi-architecture.md | 127 unpacked. 259 has unpacked and then compare it with the total number of bits that the method 287 As an example this is how a bitset is unpacked 315 unpacked bytes are available for inspection. Using the same unpacking calls that 317 manually unpacked. This is helpful for multi-function commands like Set LAN
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | temporary-source-code.rst | 15 During a build, the unpacked temporary source code used by recipes to
|
| H A D | new-machine.rst | 67 create a :ref:`ref-tasks-configure` task that configures the unpacked kernel with
|
| H A D | building.rst | 142 image to be unpacked into the ``${B}/usr/`` directory. The unpacked
|
| /openbmc/docs/architecture/code-update/ |
| H A D | code-update-deprecated.md | 37 Additionally, there are two tarballs created that can be deployed and unpacked 137 the images are unpacked.
|
| /openbmc/openbmc/poky/meta/recipes-core/images/ |
| H A D | build-appliance-image_15.0.0.bb | 45 # Because fetch2's git's unpack uses -s cloneflag, the unpacked git repo
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-fetching.rst | 162 - *unpack:* Controls whether the URL components are unpacked. If set to 163 "1", which is the default, the components are unpacked. If set to 165 when you want an archive to be copied in and not be unpacked. 208 If you specify a directory, the entire directory is unpacked. 312 renaming the output directory to which the module is unpacked. You
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | go-vendor.bbclass | 13 # downloaded during the fetch-phase and unpacked into the modules 'vendor'
|
| H A D | devtool-source.bbclass | 104 bb.warn("No source unpacked to S - either the %s recipe "
|
| H A D | externalsrc.bbclass | 120 # This is safe, as externalsrc runs with the source already unpacked.
|
| H A D | archiver.bbclass | 9 # 1) original (or unpacked) source: ARCHIVER_MODE[src] = "original" 184 # (e.g. git repositories) is "unpacked" and then put into a tarball.
|
| /openbmc/qemu/target/ppc/ |
| H A D | int_helper.c | 2037 #define VUPK(suffix, unpacked, packee, hi) \ in VUPKPX() argument 2044 for (i = 0; i < ARRAY_SIZE(r->unpacked); i++) { \ in VUPKPX() 2045 result.unpacked[i] = b->packee[i]; \ in VUPKPX() 2048 for (i = ARRAY_SIZE(r->unpacked); i < ARRAY_SIZE(r->packee); \ in VUPKPX() 2050 result.unpacked[i - ARRAY_SIZE(r->unpacked)] = b->packee[i]; \ in VUPKPX()
|
| /openbmc/qemu/target/arm/tcg/ |
| H A D | sve.decode | 1324 # SVE 64-bit gather load (scalar plus 32-bit unpacked unscaled offsets) 1325 # SVE 64-bit gather load (scalar plus 32-bit unpacked scaled offsets) 1357 # SVE 64-bit gather prefetch (scalar plus unpacked 32-bit scaled offsets) 1465 # SVE 64-bit scatter store (scalar plus unpacked 32-bit scaled offset) 1472 # SVE 64-bit scatter store (scalar plus unpacked 32-bit unscaled offset)
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | tasks.rst | 417 For more information on how source files are unpacked, see the 676 Converts the newly unpacked kernel source into a form with which the 808 After the kernel is unpacked but before it is patched, this task makes
|
| H A D | structure.rst | 603 directory. For example, the source for a particular package is unpacked, 614 unpacked to ``linux-qemux86-standard-build`` and then patched by Quilt.
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | intro.rst | 139 - downloaded a Yocto Project release and unpacked it to
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/emacs/ |
| H A D | emacs_29.1.bb | 80 # Emacs copies files to ${D} while building, which were unpacked
|
| /openbmc/openbmc/poky/meta-poky/conf/templates/default/ |
| H A D | local.conf.sample.extended | 228 # 1) original (or unpacked) source:
|
| /openbmc/openbmc/poky/documentation/overview-manual/ |
| H A D | concepts.rst | 246 assumes the script is executed from within a cloned or unpacked version 706 Each recipe has an area in the :term:`Build Directory` where the unpacked 708 recipe's unpacked source code, and has the default ``sources-unpack`` name. The 739 - :term:`UNPACKDIR`: Contains the unpacked source files for a given recipe. 764 Once source code is fetched and unpacked, BitBake locates patch files 1796 built or it could be downloaded and unpacked from somewhere. In other words,
|
| /openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
| H A D | kernel-devsrc.bb | 15 # We need the kernel to be staged (unpacked, patched and configured) before
|
| /openbmc/openbmc/poky/meta/classes-global/ |
| H A D | staging.bbclass | 252 # Manifests here are complicated. The main sysroot area has the unpacked sstate
|