| /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 | crossbuild-template.yml | 3 stage: build
7 - ccache
12 - source scripts/ci/gitlab-ci-section
13 - section_start setup "Pre-script setup"
14 - JOBS=$(expr $(nproc) + 1)
15 - cat /packages.txt
16 - section_end setup
18 - export CCACHE_BASEDIR="$(pwd)"
19 - export CCACHE_DIR="$CCACHE_BASEDIR/ccache"
20 - export CCACHE_MAXSIZE="500M"
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/dev-tools/ |
| H A D | gdb-kernel-debugging.rst | 3 .. include:: ../disclaimer-zh_CN.rst
5 :Original: Documentation/dev-tools/gdb-kernel-debugging.rst
18 ------------
20 - gdb 7.2+ (推荐版本: 7.4+) 且开启python支持 (通常发行版上都已支持)
23 ----
25 - 创建一个QEMU/KVM的linux虚拟机（详情请参考 www.linux-kvm.org 和 www.qemu.org ）。
29 - 编译内核时开启CONFIG_GDB_SCRIPTS，关闭CONFIG_DEBUG_INFO_REDUCED。
32 - 在guest环境上安装该内核。如有必要，通过在内核command line中添加“nokaslr”来关闭KASLR。
33 此外，QEMU允许通过-kernel、-append、-initrd这些命令行选项直接启动内核。
37 - 启用QEMU/KVM的gdb stub，可以通过如下方式实现
[all …]
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | gdb-kernel-debugging.rst | 6 The kernel debugger kgdb, hypervisors like QEMU or JTAG-based hardware
16 ------------
18 - gdb 7.2+ (recommended: 7.4+) with python support enabled (typically true
23 -----
25 - Create a virtual Linux machine for QEMU/KVM (see www.linux-kvm.org and
26 www.qemu.org for more details). For cross-development,
30 - Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave
34 - Install that kernel on the guest, turn off KASLR if necessary by adding
36 Alternatively, QEMU allows to boot the kernel directly using -kernel,
37 -append, -initrd command line switches. This is generally only useful if
[all …]
|
| /openbmc/qemu/tests/docker/dockerfiles/ |
| H A D | debian-all-test-cross.docker | 2 # Docker all cross-compiler target (tests only)
5 # build environments which can cross build QEMU this just installs the
7 # to build and run linux-user tests on GitLab
9 FROM docker.io/library/debian:12-slim
11 # Duplicate deb line as deb-src
12 RUN sed -in "s/Types: deb/Types: deb deb-src/g" /etc/apt/sources.list.d/debian.sources
15 apt-get update && \
16 apt-get install -y eatmydata && \
17 eatmydata apt-get dist-upgrade -y && \
18 apt build-dep -yy qemu
[all …]
|
| H A D | debian-toolchain.docker | 2 # Docker toolchain cross-compiler
4 # This dockerfile is used for building a cross-compiler toolchain.
5 # The script for building the toolchain is supplied via extra-files.
7 FROM docker.io/library/debian:11-slim
9 # Install build utilities for building gcc and glibc.
10 # ??? The build-dep isn't working, missing a number of
11 # minimal build dependiencies, e.g. libmpc.
13 RUN sed 's/^deb /deb-src /' </etc/apt/sources.list >/etc/apt/sources.list.d/deb-src.list
16 DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata && \
18 apt install -y --no-install-recommends \
[all …]
|
| H A D | debian-loongarch-cross.docker | 2 # Docker cross-compiler target
5 # https://github.com/loongson/build-tools/releases
7 FROM docker.io/library/debian:11-slim
9 # Duplicate deb line as deb-src
10 RUN cat /etc/apt/sources.list | sed "s/^deb\ /deb-src /" >> /etc/apt/sources.list
13 apt-get update && \
14 apt-get install -y eatmydata && \
15 eatmydata apt-get dist-upgrade -y && \
16 apt build-dep -yy qemu
18 RUN apt-get update && \
[all …]
|
| H A D | debian-hexagon-cross.docker | 2 # Docker Hexagon cross-compiler target
5 # needs to be able to build QEMU itself in CI we include its
6 # build-deps.
8 FROM docker.io/library/debian:11-slim
10 # Duplicate deb line as deb-src
11 RUN cat /etc/apt/sources.list | sed "s/^deb\ /deb-src /" >> /etc/apt/sources.list
12 RUN apt-get update && \
13 DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata && \
15 # Install common build utilities
16 apt-get install -y --no-install-recommends \
[all …]
|
| H A D | debian-legacy-test-cross.docker | 1 # Docker legacy cross-compiler target (tests and minimal qemu)
6 # libc6.1-dev-alpha-cross: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054412
7 # sh4-linux-user: binaries don't run with bookworm compiler
9 # As we are targeting check-tcg here we only need minimal qemu
12 FROM docker.io/library/debian:11-slim
14 # Duplicate deb line as deb-src
15 RUN cat /etc/apt/sources.list | sed "s/^deb\ /deb-src /" >> /etc/apt/sources.list
18 apt-get update && \
19 apt-get install -y eatmydata && \
20 eatmydata apt-get dist-upgrade -y && \
[all …]
|
| /openbmc/linux/tools/build/Documentation/ |
| H A D | Build.txt | 1 Build Framework
4 The perf build framework was adopted from the kernel build system, hence the
7 Basically the user provides set of 'Build' files that list objects and
8 directories to nest for specific target to be build.
10 Unlike the kernel we don't have a single build object 'obj-y' list that where
11 we setup source objects, but we support more. This allows one 'Build' file to
12 carry a sources list for multiple build objects.
15 Build framework makefiles
16 -------------------------
18 The build framework consists of 2 Makefiles:
[all …]
|
| /openbmc/openbmc-build-scripts/ |
| H A D | qemu-build.sh | 4 # This build script is for running the QEMU build in a container
9 # In Jenkins configure the git SCM 'Additional Behaviours', 'check-out to a sub
15 # WORKSPACE=$PWD/qemu ~/openbmc-build-scripts/qemu-build.sh
22 # WORKSPACE Path of the workspace directory where the build will
30 #set -x
33 http_proxy=${http_proxy:-}
35 if [ -z ${WORKSPACE+x} ]; then
40 docker_reg=${DOCKER_REG:-"public.ecr.aws/ubuntu"}
42 # Docker Image Build Variables:
43 img_name=qemu-build
[all …]
|
| 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.
22 # build, which will be written into local.conf.
24 # CONTAINER_ONLY Set to "true" if you only want to build the docker
30 # Docker Image Build Variables:
31 # BITBAKE_OPTS Set to "-c populate_sdk" or whatever other BitBake options
32 # you'd like to pass into the build.
34 # build_dir Path where the actual BitBake build occurs inside the
36 # Default: "$WORKSPACE/build"
37 # distro The distro used as the base image for the build image:
[all …]
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-execution.rst | 1 .. SPDX-License-Identifier: CC-BY-2.5
11 development kit, or even a full, board-specific bootable Linux image,
25 <bitbake-user-manual-command>`" section.
30 parallel thread execution on your build host by setting the
34 A common method to determine this value for your build host is to run
40 the number of processors, which takes into account hyper-threading.
41 Thus, a quad-core build host with hyper-threading most likely shows
57 - **Recipes:** Details about particular pieces of software.
59 - **Class Data:** An abstraction of common build information (e.g. how to
60 build a Linux kernel).
[all …]
|
| H A D | bitbake-user-manual-metadata.rst | 1 .. SPDX-License-Identifier: CC-BY-2.5
20 ----------------------
53 ----------------------------
58 - Customize a recipe that uses the variable.
60 - Change a variable's default value used in a ``*.bbclass`` file.
62 - Change the variable in a ``*.bbappend`` file to override the variable
65 - Change the variable in a configuration file so that the value
80 - For configuration changes, use the following::
82 $ bitbake -e
94 - To find changes to a given variable in a specific recipe, use the
[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`
33 …###### _Note: When your Docker is behind a proxy, add the following parameters to the build comman…
36 --build-arg http_proxy=<IP>:<PORT> --build-arg https_proxy=<IP>:<PORT>
[all …]
|
| /openbmc/openbmc/poky/documentation/overview-manual/ |
| H A D | concepts.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
8 beyond the surface of "how-to" information and reference (or look-up)
9 material. Concepts such as components, the :term:`OpenEmbedded Build System`
11 cross-development toolchains, shared state cache, and so forth are
19 :term:`OpenEmbedded-Core (OE-Core)`. This section
26 - *Recipes:* Provides details about particular pieces of software.
28 - *Class Data:* Abstracts common build information (e.g. how to build a
31 - *Configuration Data:* Defines machine-specific settings, policy
37 ":ref:`dev-manual/layers:understanding and creating layers`"
41 additional information on how these components interact during a build,
[all …]
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | setup-and-use.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
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
62 multiple command-line builds, where each build is started in its own
[all …]
|
| /openbmc/qemu/tests/docker/ |
| H A D | Makefile.include | 3 .PHONY: docker docker-help docker-test docker-clean docker-image docker-qemu-src
9 HOST_ARCH = $(shell uname -m)
10 USER = $(if $(NOUSER),,$(shell id -un))
11 UID = $(if $(NOUSER),,$(shell id -u))
15 DOCKER_DEFAULT_REGISTRY := registry.gitlab.com/qemu-project/qemu
19 RUNC ?= $(if $(shell command -v docker), docker, podman)
20 DOCKER_SCRIPT=$(SRC_PATH)/tests/docker/docker.py --engine $(RUNC)
22 CUR_TIME := $(shell date +%Y-%m-%d-%H.%M.%S.$$$$)
23 DOCKER_SRC_COPY := $(BUILD_DIR)/docker-src.$(CUR_TIME)
29 $(call quiet-command, cp "$(SRC_ARCHIVE)" $@/qemu.tar, \
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/ |
| H A D | views.py | 6 # SPDX-License-Identifier: GPL-2.0-only
22 from orm.models import Build, Target, Task, Layer, Layer_Version, Recipe
57 # Project creation and managed build enable
63 # setting this to False enables additional non-standard mimetypes
68 # or 'application/octet-stream' if the type couldn't be guessed
74 guessed_type = 'application/octet-stream'
88 # in build mode, we redirect to the command-line builds page
91 default_project_builds = Build.objects.filter(project = default_project)
93 # we only redirect to projects page if there is a user-generated project
94 num_builds = Build.objects.all().count()
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | python-development-shell.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
11 :ref:`ref-tasks-patch` are run for the
19 '/media/build1/poky/build/tmp/sysroots'
27 pydevshell> bb.build.exec_func("do_unpack", d)
30 See the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:functions you can call from within …
31 section in the BitBake User Manual for details about available functions.
33 The commands execute just as if the OpenEmbedded build
35 helpful when debugging a build or preparing software to be used with the
36 OpenEmbedded build system.
39 ``matchbox-desktop``::
[all …]
|
| /openbmc/phosphor-user-manager/docs/ |
| H A D | README.md | 1 # phosphor-user-manager
3 ## To Build
5 To build this package, do the following steps:
8 1. meson build
9 2. ninja -C build
17 …-c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d '{"data":[false,"ldap://<ldap://…
26 - First time LDAP configuration.
27 - Change the already configured Client/CA certificate
32 curl -c cjar -b cjar -k -H "Content-Type: application/octet-stream"
33 -X PUT -T <FILE> https://<BMC_IP>/xyz/openbmc_project/certs/client/ldap
[all …]
|
| /openbmc/linux/samples/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 You can build and test sample kernel code here.
14 tristate "Build trace_events examples -- loadable modules only"
20 tristate "Build custom trace event example -- loadable modules only"
26 tristate "Build trace_printk module - tests various trace_printk formats"
33 tristate "Build register_ftrace_direct() example"
41 tristate "Build register_ftrace_direct() on multiple ips example"
50 tristate "Build custom ftrace ops example"
57 tristate "Build sample module for kernel access to Ftrace instancess"
64 tristate "Build kobject examples"
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | imagefeatures.py | 4 # SPDX-License-Identifier: MIT
23 Summary: Check if non root user can connect via ssh without password
24 …Expected: 1. Connection to the image via ssh using root user without providing a password should b…
25 …2. Connection to the image via ssh using tester user without providing a password should be allowe…
26 Product: oe-core
31 …features = 'EXTRA_IMAGE_FEATURES = "ssh-server-openssh empty-root-password allow-empty-password al…
33 …features += 'EXTRA_USERS_PARAMS = "useradd -p \'\' {}; usermod -s /bin/sh {};"'.format(self.test_u…
36 # Build a core-image-minimal
37 bitbake('core-image-minimal')
39 with runqemu("core-image-minimal") as qemu:
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | tasks.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
10 build system.
12 Normal Recipe Build Tasks
17 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:tasks`" and
18 ":ref:`bitbake-user-manual/bitbake-user-manual-execution:dependencies`" sections in the
19 BitBake User Manual.
21 .. _ref-tasks-build:
24 ------------
27 tasks required to build a recipe.
29 .. _ref-tasks-compile:
[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 …]
|