| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | retain.py | 5 # SPDX-License-Identifier: MIT
22 Expected: Archive written to RETAIN_OUTDIR when build of test recipe completes
23 Product: oe-core
27 test_recipe = 'quilt-native'
29 features = 'INHERIT += "retain"\n'
30 features += 'RETAIN_DIRS_ALWAYS = "${T}"\n'
31 self.write_config(features)
33 bitbake('-c clean %s' % test_recipe)
54 Summary: Test retain class default behaviour
55 Expected: Archive written to RETAIN_OUTDIR only when build of test
[all …]
|
| /openbmc/u-boot/arch/arc/ |
| H A D | Kconfig | 5 default "arc"
8 default "arcv1" if ISA_ARCOMPACT
9 default "arcv2" if ISA_ARCV2
13 default ISA_ARCOMPACT
23 ISA for the Next Generation ARC-HS cores
29 default CPU_ARC770D if ISA_ARCOMPACT
30 default CPU_ARCHS38 if ISA_ARCV2
37 Choose this option to build an U-Boot for ARC750D CPU.
44 Choose this option to build an U-Boot for ARC770D CPU.
51 Next Generation ARC Core based on ISA-v2 ISA without MMU.
[all …]
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | hyperv.rst | 1 Hyper-V Enlightenments
6 -----------
10 guest support for such features is added simultaneously with the feature itself.
11 It may, however, be hard-to-impossible to add support for these interfaces to
14 KVM on x86 implements Hyper-V Enlightenments for Windows guests. These features
15 make Windows and Hyper-V guests think they're running on top of a Hyper-V
16 compatible hypervisor and use Hyper-V specific features.
20 -----
22 No Hyper-V enlightenments are enabled by default by either KVM or QEMU. In
25 .. parsed-literal::
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | features.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Features title
7 This chapter provides a reference of shipped machine and distro features
8 you can include as part of your image, a reference on image features you
9 can select, and a reference on :ref:`ref-features-backfill`.
11 Features provide a mechanism for working out which packages should be
13 features they want to support through the :term:`DISTRO_FEATURES` variable,
15 as ``poky.conf``, ``poky-tiny.conf``, ``poky-altcfg.conf`` and so forth.
16 Machine features are set in the :term:`MACHINE_FEATURES` variable, which is
18 features for a given machine.
[all …]
|
| H A D | variables.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 This chapter lists common variables used in the OpenEmbedded build
16 :term:`U <UBOOT_BINARY>` :term:`V <VIRTUAL-RUNTIME>`
27 ``meta/conf/machine/include/arm/arch-arm.inc`` file sets the
34 By default, BitBake does not produce empty packages. This default
39 Like all package-controlling variables, you must always use them in
43 ALLOW_EMPTY:${PN}-dev = "1"
44 ALLOW_EMPTY:${PN}-staticdev = "1"
49 When this occurs, the OpenEmbedded build system needs to use the
51 commands can co-exist.
[all …]
|
| /openbmc/openbmc/poky/meta-poky/conf/templates/default/ |
| H A D | local.conf.sample | 12 # default values are provided as comments to show people example syntax. Enabling
19 # You need to select a specific machine to target the build with. There are a selection
28 #MACHINE ?= "qemux86-64"
33 #MACHINE ?= "beaglebone-yocto"
36 #MACHINE ?= "genericx86-64"
38 # This sets the default machine to be qemux86-64 if no other machine is selected:
39 MACHINE ??= "qemux86-64"
48 # During a first build the system will download many different source code tarballs
54 # The default is a downloads directory under TOPDIR which is the build directory.
59 # Where to place shared-state files
[all …]
|
| H A D | local.conf.sample.extended | 13 # Default to setting automatically based on cpu count
19 #PARALLEL_MAKE ?= "-j 4"
21 # Default to setting automatically based on cpu count
22 #PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
24 # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
34 # If you want to get an image based on directfb without x11 alter
40 # packages at build time using qemu-native. Disabling it (by setting it to 0)
41 # will save some build time at the expense of breaking i18n on devices with
45 # If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
46 # glibc-binary-localedata-XX-YY to be a meta package depending on
[all …]
|
| /openbmc/qemu/.gitlab-ci.d/custom-runners/ |
| H A D | ubuntu-22.04-aarch64.yml | 1 # All ubuntu-22.04 jobs should run successfully in an environment
2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task
3 # "Install basic packages to build QEMU on Ubuntu 22.04"
5 ubuntu-22.04-aarch64-all-linux-static:
8 stage: build
10 - ubuntu_22.04
11 - aarch64
13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
14 - if: "$AARCH64_RUNNER_AVAILABLE"
16 - mkdir build
[all …]
|
| /openbmc/openbmc/poky/meta/conf/ |
| H A D | documentation.conf | 3 # Mail your changes to openembedded-devel@openembedded.org
8 do_build[doc] = "Default task for a recipe - depends on all other normal tasks required to 'build' …
17 do_configure[doc] = "Configures the source by enabling and disabling any build-time and configurati…
26 do_kernel_checkout[doc] = "Checks out source/meta branches for a linux-yocto style kernel"
27 do_kernel_configcheck[doc] = "Validates the kernel configuration for a linux-yocto style kernel"
28 do_kernel_configme[doc] = "Assembles the kernel configuration for a linux-yocto style kernel"
39 do_packagedata[doc] = "Creates package metadata used by the build system to generate the final pack…
44 do_rm_work[doc] = "Removes work files after the build system has finished with them"
45 do_rm_work_all[doc] = "Top-level task for removing work files after the build system has finished w…
49 do_spdx[doc] = "A build stage that takes the source code and scans it on a remote FOSSOLOGY server …
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/bearssl/ |
| H A D | bearssl_0.6.bb | 3 5246) written in C. It aims at offering the following features: \
6 algorithm implementations are constant-time by default. \
13 * Be feature-rich and extensible. SSL/TLS has many defined cipher suites \
29 file://0002-test-test_x509.c-fix-potential-overflow-issue.patch \
33 # without compile errors like
34 # <..>/ld: build/obj/ghash_pclmul.o: warning: relocation against `br_ghash_pclmul' in read-only sec…
35 CFLAGS += "-fPIC"
38 BEARSSLDLL=build/${SONAME} \
39 LDDLLFLAGS="-shared -Wl,-soname,${SONAME}" \
46 install -d ${D}/${bindir} ${D}/${libdir} ${D}/${includedir}
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | kconfig.rst | 13 SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
21 QEMU uses a simple domain-specific language to describe the dependencies
24 * new targets and boards can be added without knowing in detail the
30 * users can easily build reduced versions of QEMU that support only a subset
31 of boards or devices. For example, by default most targets will include
32 all emulated PCI devices that QEMU supports, but the build process is
36 This domain-specific language is based on the Kconfig language that
41 is instead specified in per-target files under the ``configs/``
44 QEMU; the default configuration that QEMU ships with should be okay in
48 --------------------
[all …]
|
| /openbmc/openbmc/meta-security/meta-integrity/ |
| H A D | README.md | 5 The bbappend files for some recipes (e.g. linux-yocto) in this layer need
11 If meta-integrity is included, but integrity is not enabled as a
14 You have included the meta-integritry layer, but
31 URI: git://git.openembedded.org/openembedded-core
35 URI: git://github.com/01org/meta-security/meta-integrate
36 layers: security-framework
44 yocto-patches@yoctoproject.org mailing list. When submitting patches that way,
45 make sure to copy the maintainer and add a "[meta-integrity]"
54 1. Adding the integrity layer to your build
59 1. Adding the integrity layer to your build
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-extended/bash/ |
| H A D | bash.inc | 1 SUMMARY = "An sh-compatible command language interpreter"
3 …itectures that support it, csh-like features such as history substitution and brace expansion, and…
6 DEPENDS = "ncurses bison-native virtual/libiconv"
8 inherit autotools gettext texinfo update-alternatives ptest
10 EXTRA_AUTORECONF += "--exclude=autoheader,aclocal"
11 EXTRA_OECONF = "--enable-job-control --without-bash-malloc bash_cv_wexitstatus_offset=8"
16 CFLAGS += "-DNON_INTERACTIVE_LOGIN_SHELLS"
19 CFLAGS += "-DHEREDOC_PIPESIZE=65536"
21 # Disable bracketed paste mode by default (enabled by default in bash 5.1). It
22 # causes a lot of garbage in non-interactive shells
[all …]
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 2 - local: '/.gitlab-ci.d/buildtest-template.yml'
4 build-system-alpine:
6 - .native_build_job_template
7 - .native_build_artifact_template
9 - job: amd64-alpine-container
12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu
13 MAKE_CHECK_ARGS: check-build
14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog
16 check-system-alpine:
19 - job: build-system-alpine
[all …]
|
| H A D | crossbuilds.yml | 2 - local: '/.gitlab-ci.d/crossbuild-template.yml'
4 cross-armhf-user:
7 job: armhf-debian-cross-container
9 IMAGE: debian-armhf-cross
11 cross-arm64-system:
14 job: arm64-debian-cross-container
16 IMAGE: debian-arm64-cross
18 cross-arm64-user:
21 job: arm64-debian-cross-container
23 IMAGE: debian-arm64-cross
[all …]
|
| /openbmc/qemu/scripts/ |
| H A D | meson-buildoptions.py | 4 # user build options introspection data
16 # but WITHOUT ANY WARRANTY; without even the implied warranty of
28 # Options with nonstandard names (e.g. --with/--without) or OS-dependent
40 "coroutine_backend": "with-coroutine",
41 "debug": "debug-info",
42 "malloc": "enable-malloc",
43 "pkgversion": "with-pkgversion",
45 "qemu_suffix": "with-suffix",
46 "trace_backends": "enable-trace-backends",
47 "trace_file": "with-trace-file",
[all …]
|
| /openbmc/u-boot/arch/x86/ |
| H A D | Kconfig | 5 default "x86"
8 prompt "Run U-Boot in 32/64-bit mode"
9 default X86_RUN_32BIT
11 U-Boot can be built as a 32-bit binary which runs in 32-bit mode
12 even on 64-bit machines. In this case SPL is not used, and U-Boot
13 runs directly from the reset vector (via 16-bit start-up).
15 Alternatively it can be run as a 64-bit binary, thus requiring a
16 64-bit machine. In this case SPL runs in 32-bit mode (via 16-bit
17 start-up) then jumps to U-Boot in 64-bit mode.
19 For now, 32-bit mode is recommended, as 64-bit is still
[all …]
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | common.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
12 incorporating out-of-tree modules.
19 Preparing the Build Host to Work on the Kernel
22 Before you can do any kernel development, you need to be sure your build
24 set up, see the ":doc:`/dev-manual/start`" section in
28 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
37 ":ref:`dev-manual/start:checking out by branch in poky`" and
38 ":ref:`dev-manual/start:checking out by tag in poky`"
42 :ref:`devtool <sdk-manual/extensible:using \`\`devtool\`\` in your sdk workflow>`
47 ------------------------------------------
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | building.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
6 This section describes various build procedures, such as the steps
7 needed for a simple build, building a target for multiple configurations,
13 In the development environment, you need to build an image whenever you
16 you to build an image within the Yocto Project. This section presents
17 the basic steps you need to build a simple image using BitBake from a
18 build host running Linux.
22 - For information on how to build an image using
24 :doc:`/toaster-manual/index`.
26 - For information on how to use ``devtool`` to build images, see the
[all …]
|
| /openbmc/u-boot/test/py/ |
| H A D | README.md | 1 # U-Boot pytest suite
5 This tool aims to test U-Boot by executing U-Boot shell commands using the
6 console interface. A single top-level script exists to execute or attach to the
7 U-Boot console, run the entire script of tests against it, and summarize the
10 - Testing is performed in the same way a user or script would interact with
11 U-Boot; there can be no disconnect.
12 - There is no need to write or embed test-related code into U-Boot itself.
13 It is asserted that writing test-related code in Python is simpler and more
15 - It is reasonably simple to interact with U-Boot in this way.
19 The test suite is implemented using pytest. Interaction with the U-Boot console
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.fdt-control | 1 # SPDX-License-Identifier: GPL-2.0+
5 Device Tree Control in U-Boot
8 This feature provides for run-time configuration of U-Boot via a flat
9 device tree (fdt). U-Boot configuration has traditionally been done
11 make it possible for a single U-Boot binary to support multiple boards,
16 The fdt is a convenient vehicle for implementing run-time configuration
23 format, and a library is already available in U-Boot (libfdt) for
27 and embedding it in your U-Boot image. This is useful since it allows
28 U-Boot to configure itself according to what it finds there. If you have
30 the features of each board in the device tree file, and have a single
[all …]
|
| /openbmc/u-boot/tools/binman/ |
| H A D | README | 1 # SPDX-License-Identifier: GPL-2.0+
5 ------------
8 For example, we may have SPL, U-Boot, a device tree and an environment area
12 So far U-Boot has not provided a way to handle creating such images in a
13 general way. Each SoC does what it needs to build an image, often packing or
14 concatenating images in the U-Boot build system.
17 SPL + U-Boot combinations, to more complex arrangements with many parts.
21 ------------
29 Features
30 --------
[all …]
|
| /openbmc/qemu/ |
| H A D | configure | 14 source_path=$(cd "$(dirname -- "$0")"; pwd)
16 if test "$PWD" -ef "$source_path"
18 echo "Using './build' as the directory for build output"
20 MARKER=build/auto-created-by-configure
22 if test -e build
24 if test -f $MARKER
26 rm -rf build
28 echo "ERROR: ./build dir already exists and was not previously created by configure"
33 if ! mkdir build || ! touch $MARKER
35 echo "ERROR: Could not create ./build directory. Check the permissions on"
[all …]
|
| /openbmc/qemu/docs/system/ |
| H A D | introduction.rst | 7 ---------------------------
14 .. list-table:: Supported Accelerators
15 :header-rows: 1
17 * - Accelerator
18 - Host OS
19 - Host Architectures
20 * - KVM
21 - Linux
22 - Arm (64 bit only), MIPS, PPC, RISC-V, s390x, x86
23 * - Xen
[all …]
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | qpl-compression.rst | 4 The Intel Query Processing Library (Intel ``QPL``) is an open-source library to
5 provide compression and decompression features and it is based on deflate
8 The ``QPL`` compression relies on Intel In-Memory Analytics Accelerator(``IAA``)
9 and Shared Virtual Memory(``SVM``) technology, they are new features supported
21 +----------------+ +------------------+
22 | MultiFD Thread | |accel-config tool |
23 +-------+--------+ +--------+---------+
27 +-------+--------+ | Setup IAA
29 +-------+---+----+ |
31 | +-------------+-------+
[all …]
|