/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 …]
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | system-requirements.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 4 System Requirements 18 ":ref:`overview-manual/development-environment:the yocto project development environment`" 21 If you want to use the Yocto Project to quickly build an image without 23 :doc:`/brief-yoctoprojectqs/index` document. You can find "how-to" 24 information in the :doc:`/dev-manual/index`. You can find Yocto Project overview 25 and conceptual information in the :doc:`/overview-manual/index`. 30 the :ref:`ref-manual/resources:links and related documentation` section. 35 To build an image such as ``core-image-sato`` for the ``qemux86-64`` machine, 36 you need a system with at least &MIN_DISK_SPACE; Gbytes of free disk space. [all …]
|
/openbmc/openbmc/meta-arm/meta-arm-systemready/ |
H A D | README.md | 1 # meta-arm-systemready Yocto Layer 7 top-level meta-arm [README.md](../README.md) file. 18 [`meta-arm-bsp`][] layer in the top-level meta-arm defines the 19 [`fvp-base`][] machine, which can be used with the recipes provided by this 20 layer to build the firmware, run the [Arm SystemReady IR][] ACS tests, and 22 with their BSP layer to perform the same build and tests. 24 ### Firmware Build 26 The `arm-systemready-firmware.bb` recipe is to build the firmware. It requires 28 to list the build dependencies. 42 `edk2-test-parser-native.bb` and `arm-systemready-scripts-native.bb` recipes [all …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/snapper/ |
H A D | snapper_0.11.2.bb | 1 SUMMARY = "Snapper is a tool for Linux file system snapshot management" 2 HOMEPAGE = "https://github.com/openSUSE/snapper" 3 LICENSE = "GPL-2.0-only" 6 DEPENDS = "acl boost btrfs-tools dbus e2fsprogs json-c libxml2 lvm2 ncurses zlib" 8 # Build separation is slightly broken 9 inherit autotools-brokensep pkgconfig gettext 12 git://github.com/openSUSE/snapper.git;protocol=https;branch=master \ 13 file://0001-Include-linux-types.h-for-__u16-__u32-__u64-type.patch \ 14 file://0002-Use-statvfs-instead-of-statvfs64.patch \ 20 EXTRA_OECONF += "--disable-zypp" [all …]
|
/openbmc/openbmc/poky/documentation/toaster-manual/ |
H A D | setup-and-use.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 12 Once you have set up the Yocto Project and installed the Toaster system 13 dependencies as described in the ":ref:`toaster-manual/start:Preparing to Use 22 Once in that directory, source the build environment script:: 24 $ source oe-init-build-env 26 Next, from the :term:`Build Directory` (e.g. ``poky/build``), start Toaster 33 ":ref:`toaster-manual/setup-and-use:using the toaster web interface`". 55 - Capturing a command-line build's statistics into the Toaster database 58 - Capturing a command-line build's statistics when the Toaster server 61 - Having one instance of the Toaster web server track and capture [all …]
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
H A D | user-guide.rst | 2 # Copyright (c) 2022-2024, Arm Limited. 4 # SPDX-License-Identifier: MIT 7 Build, Flash and Run 11 ------ 12 The Corstone-1000 software stack uses the `Yocto Project <https://www.yoctoproject.org/>`__ to build 13 a tiny Linux distribution suitable for the Corstone-1000 platform (kernel and initramfs filesystem … 14 The Yocto Project relies on the `BitBake <https://docs.yoctoproject.org/bitbake.html#bitbake-docume… 15 tool as its build tool. Please see `Yocto Project documentation <https://docs.yoctoproject.org/>`__ 19 ------------- 24 The following prerequisites must be available on the host system: [all …]
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-5.1.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 7 --------------------------------- 12 .. _migration-5.1-workdir-changes: 27 should be changed to :term:`S`. These are commonly in :ref:`ref-tasks-compile`, 28 :ref:`ref-tasks-compile`, :ref:`ref-tasks-install` and :term:`LIC_FILES_CHKSUM`. 35 These are commonly in :ref:`ref-tasks-compile` and :ref:`ref-tasks-install` 46 Files from :ref:`ref-tasks-unpack` now unpack to ``WORKDIR/sources-unpack/`` 50 subdirectory exists in ``sources-unpack`` after :ref:`ref-tasks-unpack` runs, 54 based recipes. Keeping all sources under ``sources-unpack`` wasn't considered 56 :ref:`ref-tasks-unpack` task output from :term:`WORKDIR`. [all …]
|
H A D | migration-4.2.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 7 ------------------------------------ 12 .. _migration-4.2-supported-distributions: 19 - Fedora 36 and 37 20 - AlmaLinux 8.7 and 9.1 21 - OpenSuse 15.4 25 - Debian 10.x 26 - Fedora 34 and 35 27 - AlmaLinux 8.5 29 See :ref:`all supported distributions <system-requirements-supported-distros>`. [all …]
|
H A D | migration-5.0.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 7 ------------------------------------ 15 - :doc:`/migration-guides/migration-4.3` 16 - :doc:`/migration-guides/migration-4.2` 17 - :doc:`/migration-guides/migration-4.1` 18 - :doc:`/migration-guides/migration-4.0` 19 - :doc:`/migration-guides/migration-3.4` 20 - :doc:`/migration-guides/migration-3.3` 21 - :doc:`/migration-guides/migration-3.2` 23 .. _migration-5.0-supported-kernel-versions: [all …]
|
H A D | release-notes-4.1.3.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 3 Release notes for Yocto-4.1.3 (Langdale) 4 ---------------------------------------- 6 Security Fixes in Yocto-4.1.3 9 - apr-util: Fix :cve_nist:`2022-25147` 10 - apr: Fix :cve_nist:`2022-24963` and :cve_nist:`2022-28331` 11 - bind: Fix :cve_nist:`2022-3094`, :cve_nist:`2022-3736` and :cve_nist:`2022-3924` 12 - curl: Fix :cve_nist:`2022-43551` and :cve_nist:`2022-43552` 13 - dbus: Fix :cve_nist:`2022-42010`, :cve_nist:`2022-42011` and :cve_nist:`2022-42012` 14 - git: Fix :cve_nist:`2022-23521`, :cve_nist:`2022-39253`, :cve_nist:`2022-39260` and :cve_nist:`… [all …]
|
/openbmc/qemu/docs/about/ |
H A D | build-platforms.rst | 1 .. _Supported-build-platforms: 3 Supported build platforms 7 platforms. This appendix outlines which platforms are the major build 25 support for those backports, unless the feature is auto-detectable in a 33 ---------------------------- 37 .. list-table:: 38 :header-rows: 1 40 * - CPU Architecture 41 - Accelerators 42 * - Arm [all …]
|
/openbmc/linux/scripts/ |
H A D | sphinx-pre-install | 2 # SPDX-License-Identifier: GPL-2.0-or-later 5 # Copyright (c) 2017-2020 Mauro Carvalho Chehab <mchehab@kernel.org> 35 my $rec_version = "1.7.9"; # PDF won't build here 48 # List of required texlive packages on Fedora and OpenSuse 52 'amsfonts.sty' => 'texlive-amsfonts', 53 'amsmath.sty' => 'texlive-amsmath', 54 'amssymb.sty' => 'texlive-amsfonts', 55 'amsthm.sty' => 'texlive-amscls', 56 'anyfontsize.sty' => 'texlive-anyfontsize', 57 'atbegshi.sty' => 'texlive-oberdiek', [all …]
|
/openbmc/openbmc/poky/documentation/brief-yoctoprojectqs/ |
H A D | index.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 4 Yocto Project Quick Build 11 image build using the Yocto Project. The document also introduces how to 12 configure a build for specific hardware. You will use Yocto Project to 13 build a reference embedded OS called Poky. 17 - The examples in this paper assume you are using a native Linux 18 system running a recent Ubuntu Linux distribution. If the machine 19 you want to use Yocto Project on to build an image 20 (:term:`Build Host`) is not 21 a native Linux system, you can still perform these steps by using [all …]
|
/openbmc/qemu/docs/devel/ |
H A D | build-system.rst | 2 The QEMU build system architecture 6 QEMU build system. As with projects using GNU autotools, the QEMU build 7 system has two stages; first the developer runs the "configure" script 8 to determine the local build environment characteristics, then they run 9 "make" to build the project. This is about where the similarities with 12 The two general ways to perform a build are as follows: 14 - build artifacts outside of QEMU source tree entirely:: 17 mkdir build 18 cd build 22 - build artifacts in a subdir of QEMU source tree:: [all …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/nss/ |
H A D | nss_3.107.bb | 3 designed to support cross-platform development of \ 4 security-enabled client and server applications. \ 11 DEPENDS = "sqlite3 nspr zlib nss-native" 12 DEPENDS:class-native = "sqlite3-native nspr-native zlib-native" 14 LICENSE = "(MPL-2.0 & MIT) | (MPL-2.0 & GPL-2.0-or-later & MIT) | (MPL-2.0 & LGPL-2.1-or-later & MI… 18 file://nss/lib/freebl/mpi/doc/LICENSE-MPL;md5=5d425c8f3157dbf212db2ec53d9e5132 \ 21 VERSION_DIR = "${@d.getVar('BP').upper().replace('-', '_').replace('.', '_') + '_RTM'}" 25 file://blank-cert9.db \ 26 file://blank-key4.db \ 27 file://system-pkcs11.txt \ [all …]
|
/openbmc/openbmc/poky/meta/recipes-support/libgpg-error/libgpg-error/ |
H A D | pkgconfig.patch | 3 Date: Wed, 21 Aug 2024 20:03:29 -0700 6 Upstream-Status: Inappropriate [gnupg upstream will not take this, it has been tried with other com… 10 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> 13 Signed-off-by: Armin Kuster <akuster808@gmail.com> 14 Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com> 17 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> 18 --- 19 src/gpg-error.m4 | 200 ++--------------------------------------------- 20 1 file changed, 5 insertions(+), 195 deletions(-) 22 diff --git a/src/gpg-error.m4 b/src/gpg-error.m4 [all …]
|
/openbmc/openbmc/poky/meta/recipes-support/pinentry/pinentry-1.3.1/ |
H A D | gpg-error_pkconf.patch | 4 Subject: [PATCH] Add gtk+, avahi, dbus-0.34 (.36 coming soon) and 6 Convert to pkg-config support to match changes done to 7 the gpg-error recipe for gpg-error.pc generation. 9 Upstream-Status: Inappropriate [OE specific] 11 Signed-off-by: Armin Kuster <akuster@mvista.com> 12 --- 13 m4/gpg-error.m4 | 184 ++---------------------------------------------- 14 1 file changed, 5 insertions(+), 179 deletions(-) 16 diff --git a/m4/gpg-error.m4 b/m4/gpg-error.m4 18 --- a/m4/gpg-error.m4 [all …]
|
/openbmc/openbmc/poky/documentation/test-manual/ |
H A D | runtime-testing.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 7 The OpenEmbedded build system makes available a series of automated 11 run commands on the target system over SSH. This section describes how 16 Yocto Project, see the ":ref:`ref-manual/release-process:testing and quality assurance`" 28 ------------------------------ 32 - *Set up to avoid interaction with sudo for networking:* To 35 - Add ``NOPASSWD`` for your user in ``/etc/sudoers`` either for all 36 commands or just for ``runqemu-ifup``. You must provide the full 45 - Manually configure a tap interface for your system. 47 - Run as root the script in ``scripts/runqemu-gen-tapdevs``, which [all …]
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | start.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 9 using the Yocto Project, how to set up a :ref:`build 10 host <dev-manual/start:preparing the build host>`, how to locate 25 you get the results you want. The procedure is high-level and presents 29 You can build off these steps and customize the procedure to fit any 41 - *Application Developer:* This type of developer does application 44 - *Core System Developer:* This type of developer works on the 45 contents of the operating system image itself. 47 - *Build Engineer:* This type of developer manages Autobuilders and 49 situations might need a Build Engineer. [all …]
|
/openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
H A D | runtime_test.py | 4 # SPDX-License-Identifier: MIT 24 Product: oe-core 35 # Build tesexport for core-image-minimal 36 bitbake('core-image-minimal') 37 bitbake('-c testexport core-image-minimal') 39 testexport_dir = get_bb_var('TEST_EXPORT_DIR', 'core-image-minimal') 45 with runqemu('core-image-minimal') as qemu: 47 test_path = os.path.join(testexport_dir, "oe-test") 50 cmd = ("%s runtime --test-data-file %s --packages-manifest %s " 51 "--target-ip %s --server-ip %s --quiet" [all …]
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | quickly-build-trimmed-linux.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) 5 How to quickly build a trimmed Linux kernel 8 This guide explains how to swiftly build Linux kernels that are ideal for 9 testing purposes, but perfectly fine for day-to-day use, too. 15 section below: it contains a step-by-step guide, which is more detailed, but 20 If your system uses techniques like Secure Boot, prepare it to permit starting 21 self-compiled Linux kernels; install compilers and everything else needed for 24 you then use to configure, build and install your own kernel:: 26 git clone --depth 1 -b master \ 30 # Hint: it's recommended to tag your build at this point. See below for details. [all …]
|
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
H A D | bitbake-user-manual-ref-variables.rst | 1 .. SPDX-License-Identifier: CC-BY-2.5 17 - The variables listed in this glossary are specific to BitBake. 20 - Also, variables exist in other systems that use BitBake (e.g. The 31 attempt to build. Instead, BitBake assumes these recipes have already 34 In OpenEmbedded-Core, :term:`ASSUME_PROVIDED` mostly specifies native 35 tools that should not be built. An example is ``git-native``, which 37 rather than building ``git-native``. 41 :ref:`Azure Storage fetcher <bitbake-user-manual/bitbake-user-manual-fetching:fetchers>` 43 and gain access to non-public artifacts:: 45 AZ_SAS = ""se=2021-01-01&sp=r&sv=2018-11-09&sr=c&skoid=<skoid>&sig=<signature>"" [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/openbmc/poky/meta/classes-global/ |
H A D | sanity.bbclass | 4 # SPDX-License-Identifier: MIT 43 SANITY_DIFF_TOOL ?= "diff -u" 115 if start != -1 and (len(bbpath_line) != (start + 1)): 147 # Handle rename of meta-yocto -> meta-poky 148 # This marks the start of separate version numbers but code is needed in OE-Core 152 if 'meta-yocto' in layers: 155 index, meta_yocto_line = sanity_conf_find_line(r'.*meta-yocto[\'"\s\n]', lines) 157 lines[index] = meta_yocto_line.replace('meta-yocto', 'meta-poky') 188 bb.fatal(""" OE-core's config sanity checker detected a potential misconfiguration. 202 overrides = localdata.getVar("OVERRIDES", False) + ":virtclass-multilib-" + multilib [all …]
|
/openbmc/linux/arch/x86/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 4 bool "64-bit kernel" if "$(ARCH)" = "x86" 7 Say yes to build a 64-bit kernel - formerly known as x86_64 8 Say no to build a 32-bit kernel - formerly known as i386 13 # Options that are inherently 32-bit kernel only: 27 # Options that are inherently 64-bit kernel only: 54 # ported to 32-bit as well. ) 141 # Word-size accesses may read uninitialized data past the trailing \0 315 default "elf32-i386" if X86_32 316 default "elf64-x86-64" if X86_64 [all …]
|