| /openbmc/qemu/.gitlab-ci.d/custom-runners/ |
| H A D | ubuntu-22.04-s390x.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-s390x-all-linux:
8 stage: build
10 - ubuntu_22.04
11 - s390x
13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
14 - if: "$S390X_RUNNER_AVAILABLE"
16 - mkdir build
[all …]
|
| 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/docs/testing/ |
| H A D | run-test-docker.md | 6 ## Build Docker Image
18 3. Clone openbmc-build-scripts repository.
20 `git clone https://github.com/openbmc/openbmc-build-scripts`
22 4. Change directory to openbmc-build-scripts.
24 `cd openbmc-build-scripts`
26 5. Build the Docker image required to execute the robot tests (it may take close
28 "openbmc/ubuntu-robot-qemu". You can check images using "docker images"
31 `./scripts/build-qemu-robot-docker.sh`
34 the build command (use proper IP and PORT values.)
37 --build-arg http_proxy=<IP>:<PORT> --build-arg https_proxy=<IP>:<PORT>
[all …]
|
| /openbmc/docs/development/ |
| H A D | dev-environment.md | 7 **Prerequisites:** Current Linux, Mac, or Windows system
15 walk you through utilizing bitbake to build OpenBMC firmware and boot it in
18 Bitbake is the build engine used by Yocto and OpenBMC to build its custom Linux
19 distribution for a system. QEMU is a software emulator that can be used to run
25 For testing purposes, this guide uses the Romulus system as the default because
26 this is the system tested for each CI job, which means it's the most stable.
33 The recommended OpenBMC development environment is the latest Ubuntu LTS
41 [VMware](https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html)
49 OpenBMC continuous integration utilizes docker to build its images. This is
51 [build-setup.sh](https://github.com/openbmc/openbmc-build-scripts/blob/master/build-setup.sh)
[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/qemu/.gitlab-ci.d/ |
| H A D | custom-runners.yml | 2 # registered on machines that match their operating system names,
10 # gitlab-runner. To avoid problems that gitlab-runner can cause while
20 GIT_FETCH_EXTRA_FLAGS: --no-tags --prune --quiet
22 name: "$CI_JOB_NAME-$CI_COMMIT_REF_SLUG"
26 - build/build.ninja
27 - build/meson-logs
29 junit: build/meson-logs/testlog.junit.xml
32 - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml'
33 - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-aarch64.yml'
34 - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-aarch32.yml'
|
| 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-build-scripts/scripts/ |
| H A D | build-qemu-robot-docker.sh | 1 #!/bin/bash -xe
3 # Build the required docker image to run QEMU and Robot test cases
6 # UBUNTU_MIRROR: <optional, the URL of a mirror of Ubuntu to override the
12 # instead of our default (public.ecr.aws/ubuntu)
16 # default is openbmc/ubuntu-robot-qemu
17 # param2: <optional, the distro to build a docker image against>
19 set -uo pipefail
21 http_proxy=${http_proxy:-}
23 DOCKER_IMG_NAME=${1:-"openbmc/ubuntu-robot-qemu"}
24 DISTRO=${2:-"ubuntu:plucky"}
[all …]
|
| H A D | build-unit-test-docker | 3 # Build the required docker image to run package unit tests
7 # default is openbmc/ubuntu-unit-test
8 # DISTRO: <optional, the distro to build a docker image against>
9 # FORCE_DOCKER_BUILD: <optional, a non-zero value with force all Docker
13 # BRANCH: <optional, branch to build from each of the openbmc/
17 # UBUNTU_MIRROR: <optional, the URL of a mirror of Ubuntu to override the
21 # instead of our default (public.ecr.aws/ubuntu)
35 # typing.Dict is used for type-hints.
41 # System may have docker or it may have podman, try docker first
51 print("No docker or podman found on system")
[all …]
|
| /openbmc/openbmc-build-scripts/ |
| H A D | build-setup.sh | 4 # This build script is for running the OpenBMC builds as Docker containers.
9 # build_scripts_dir The path of the openbmc-build-scripts directory.
17 # in system
18 # UBUNTU_MIRROR [optional] The URL of a mirror of Ubuntu to override the
22 # build, which will be written into local.conf.
24 # CONTAINER_ONLY Set to "true" if you only want to build the docker
27 # instead of our default (public.ecr.aws/ubuntu)
31 # Docker Image Build Variables:
32 # BITBAKE_OPTS Set to "-c populate_sdk" or whatever other BitBake options
33 # you'd like to pass into the build.
[all …]
|
| H A D | run-qemu-robot-test.sh | 1 #!/bin/bash -xe
4 # This script is for starting QEMU against the input build and running the
11 # imported from. Generally, this is the build directory
12 # that is generated by the OpenBMC build-setup.sh script
14 # Example: /home/builder/workspace/openbmc-build/build.
23 # DOCKER_IMG_NAME = Defaults to openbmc/ubuntu-robot-qemu, the name the
25 # OBMC_BUILD_DIR = Defaults to /tmp/openbmc/build, the path to the
26 # directory where the UPSTREAM_WORKSPACE build files will
27 # be mounted to. Since the build containers have been
31 # paths in the original build directory. If the build
[all …]
|
| /openbmc/qemu/tests/vm/ |
| H A D | Makefile.include | 3 # Hack to allow running in an unconfigured build tree
9 VM_VENV = check-venv
12 .PHONY: vm-build-all vm-clean-all
14 EFI_AARCH64 = $(wildcard $(BUILD_DIR)/pc-bios/edk2-aarch64-code.fd)
20 ARM64_IMAGES += ubuntu.aarch64 centos.aarch64
24 HOST_ARCH = $(shell uname -m)
31 IMAGES_DIR := $(HOME)/.cache/qemu-vm/images
37 HAVE_PYTHON_YAML = $(shell $(PYTHON) -c "import yaml" 2> /dev/null && echo yes)
40 # 'vm-help' target was historically named 'vm-test'
41 vm-help vm-test:
[all …]
|
| H A D | ubuntuvm.py | 3 # Ubuntu VM testing library
10 # Originally based on ubuntu.i386 Fam Zheng <famz@redhat.com>
13 # the COPYING file in the top-level directory.
22 self.login_prompt = "ubuntu-{}-guest login:".format(self.arch)
26 """Build an Ubuntu VM image. The child class will
31 subprocess.check_call(["cp", "-f", os_img, img_tmp])
35 self.boot(img_tmp, extra_args = [ "-device", "VGA", "-cdrom", ci_img, ])
39 cmd="chmod -x /etc/update-motd.d/*")
42 cmd="ls /var/lib/cloud/instance/boot-finished")
43 self.ssh_root("touch /etc/cloud/cloud-init.disabled")
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.x86 | 1 # SPDX-License-Identifier: GPL-2.0+
6 U-Boot on x86
9 This document describes the information about U-Boot running on x86 targets,
10 including supported boards, build instructions, todo list, etc.
13 ------
14 U-Boot supports running as a coreboot [1] payload on x86. So far only Link
17 most of the low-level details.
19 U-Boot is a main bootloader on Intel Edison board.
21 U-Boot also supports booting directly from x86 reset vector, without coreboot.
23 'bare metal', U-Boot acts like a BIOS replacement. The following platforms
[all …]
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | openbmc_test_tools.md | 8 $ ipmitool -V
14 HTX is a suite of test tools for stressing system hardware. It is routinely used
16 [README](https://github.com/open-power/HTX)
21 [README](https://github.com/openbmc/phosphor-logging/blob/master/README.md#remote-logging-via-rsysl…
25 Pre-requisite: A Power Linux system is required.
27 - Obtain the SEL (System Error Log) parser tools:
28 - Go to https://openpower.xyz/job/openpower/job/openpower-op-build/
29 - Click the link for the BMC system of interest (e.g. witherspoon)
30 - Click the "host_fw_debug.tar" link in order to download the tar file.
31 - On your Power Linux system, untar the file with the following command:
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/.github/workflows/docker-images/yocto-builder/ |
| H A D | Dockerfile | 1 # SPDX-FileCopyrightText: Andrei Gherzan <andrei.gherzan@huawei.com>
3 # SPDX-License-Identifier: MIT
5 FROM ubuntu:22.04
8 RUN apt-get update -qq
9 RUN apt-get install -y eatmydata
11 # Yocto/OE build host dependencies
15 RUN eatmydata apt-get install -qq -y \
16 build-essential chrpath cpio debianutils diffstat file gawk gcc \
17 git iputils-ping libacl1 liblz4-tool locales python3 python3-git \
18 python3-jinja2 python3-pexpect python3-pip python3-subunit socat \
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | bmaptool.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 `bmaptool`, which is integrated into the OpenEmbedded build system.
11 system image files much faster.
15 - If you are using Ubuntu or Debian distributions, you can install
16 the ``bmap-tools`` package using the following command and then
20 $ sudo apt install bmap-tools
22 - If you are unable to install the ``bmap-tools`` package, you will
23 need to build `bmaptool` before using it. Use the following command::
25 $ bitbake bmaptool-native -caddto_recipe_sysroot
36 #. *Get Your Image:* Either have your image ready (pre-built with the
[all …]
|
| 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/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/.gitlab-ci.d/opensbi/ |
| H A D | Dockerfile | 2 # Docker image to cross-compile OpenSBI firmware binaries
4 FROM ubuntu:18.04
8 # Install packages required to build OpenSBI
13 apt install --assume-yes --no-install-recommends \
14 build-essential \
15 ca-certificates \
22 rm -rf /var/lib/apt/lists/*
24 # Manually install the kernel.org "Crosstool" based toolchains for gcc-8.3
25 RUN wget -O - \
26 …ge.kernel.org/pub/tools/crosstool/files/bin/x86_64/8.3.0/x86_64-gcc-8.3.0-nolibc-riscv32-linux.tar…
[all …]
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | start.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
9 This chapter describes how you need to prepare your system in order to
12 Setting Up the Basic System Requirements
15 Before you can use Toaster, you need to first set up your build system
17 ":ref:`dev-manual/start:preparing the build host`" section of
18 the Yocto Project Development Tasks Manual. For Ubuntu/Debian, you might
21 $ sudo apt install python3-pip
23 Establishing Toaster System Dependencies
27 requirements file named ``toaster-requirements.txt`` defines the Python
31 ``poky/bitbake/toaster-requirements.txt``). The dependencies appear in a
[all …]
|
| 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-tools/dbus-vis/ |
| H A D | README.md | 1 # dbus-vis
8 ## Build section in dbus-vis
16 To build and run, a user would first need to install node.js and npm (Node.js
17 package manager), and then checkout `dbus-pcap` to this folder. To install
18 node.js on a Ubuntu/Debian-based system:
24 $ node --version
26 $ npm --version
30 Then, with `npm`, `node.js` installed and `dbus-pcap` downloaded to this folder,
44 dbus-monitor outputs)
53 6. If something happens, manual clean-up might be needed, such as stopping
[all …]
|
| /openbmc/qemu/ |
| H A D | .patchew.yml | 1 ---
91 {% elif test == "docker-mingw@fedora" or test == "docker-quick@centos8" or test == "asan" %}
94 This series failed the {{ test }} build test. Please find the testing commands and
104 This series failed build test on {{test}} host. Please find the details below.
115 ---
117 Please send your feedback to patchew-devel@redhat.com
126 time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
127 docker-quick@centos8:
133 time make docker-test-quick@centos8 SHOW_ENV=1 J=14 NETWORK=1
140 git rev-parse base > /dev/null || exit 0
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci-runners.rst.inc | 11 be set up with GitLab's "agent", called gitlab-runner, which will take
14 gitlab-runner, is called a "custom runner".
18 .gitlab-ci.d/custom-runners.yml
25 -------------------
41 Build environment
44 The ``scripts/ci/setup/$DISTRO/build-environment.yml`` Ansible
55 ansible-playbook -i inventory $DISTRO/build-environment.yml
59 by ``sudo``. If necessary, please refer to ``ansible-playbook``
60 options such as ``--become``, ``--become-method``, ``--become-user``
61 and ``--ask-become-pass``.
[all …]
|