| /qemu/contrib/gitdm/ |
| H A D | filetypes.txt | 31 # ie. we want ltmain.sh -> 'build' instead of 'code'.
36 order build,interface,tests,code,documentation,devel-doc,blobs
105 filetype build configure.*$
106 filetype build Makefile$
107 filetype build Makefile\.*$
108 filetype build config$
109 filetype build conf$
110 filetype build \.cfg$
111 filetype build \.mk$
112 filetype build \.mak$
[all …]
|
| /qemu/roms/ |
| H A D | Makefile | 79 bios: build-seabios-config-seabios-128k \
80 build-seabios-config-seabios-256k \
81 build-seabios-config-seabios-microvm
88 seavgabios-isavga: build-seabios-config-vga-isavga
91 seavgabios-%: build-seabios-config-vga-%
94 build-seabios-config-%: config.%
113 pxe-rom-%: build-pxe-roms
118 efi-rom-%: build-pxe-roms build-efi-roms edk2-basetools
124 build-pxe-roms:
129 build-efi-roms: build-pxe-roms
[all …]
|
| H A D | edk2-build.config | 39 [build.ovmf.i386]
40 desc = ovmf build (32-bit)
49 [build.ovmf.i386.secure]
50 desc = ovmf build (32-bit, secure boot)
62 [build.ovmf.x86_64]
63 desc = ovmf build (64-bit)
71 [build.ovmf.x86_64.secure]
72 desc = ovmf build (64-bit, secure boot)
81 [build.ovmf.microvm]
82 desc = ovmf build for microvm
[all …]
|
| H A D | edk2-build.py | 49 def get_toolchain(cfg, build): argument
50 if cfg.has_option(build, 'tool'):
51 return cfg[build]['tool']
179 def build_one(cfg, build, jobs = None, silent = False, nologs = False): argument
180 b = cfg[build]
183 cmdline += [ '-t', get_toolchain(cfg, build) ]
218 build + '.' + tgt,
228 get_toolchain(cfg, build),
320 for build in cfg.sections():
321 if not build.startswith('build.'):
[all …]
|
| /qemu/tests/docker/dockerfiles/ |
| H A D | debian-toolchain.docker | 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.
28 apt build-dep -yy --arch-only gcc glibc
30 ADD build-toolchain.sh /root/build-toolchain.sh
32 RUN cd /root && ./build-toolchain.sh
34 # Throw away the extra toolchain build deps, the downloaded source,
35 # and the build trees by restoring the original image,
|
| H A D | emsdk-wasm32-cross.docker | 11 FROM emscripten/emsdk:$EMSDK_VERSION_QEMU AS build-base
22 build-essential \
26 ninja-build \
29 RUN mkdir /build
30 WORKDIR /build
49 FROM build-base AS zlib-dev
58 FROM build-base AS libffi-dev
72 FROM build-base AS pixman-dev
93 FROM build-base AS glib-dev
143 FROM build-base
|
| H A D | debian-hexagon-cross.docker | 5 # needs to be able to build QEMU itself in CI we include its
6 # build-deps.
15 # Install common build utilities
24 ninja-build \
29 # Install QEMU build deps for use in CI
31 apt build-dep -yy --arch-only qemu && \
|
| H A D | debian-loongarch-cross.docker | 5 # https://github.com/loongson/build-tools/releases
16 apt build-dep -yy qemu
22 build-essential \
31 ninja-build \
40 RUN curl -#SL https://github.com/loongson/build-tools/releases/download/2023.08.08/CLFS-loongarch64…
|
| H A D | debian-all-test-cross.docker | 5 # build environments which can cross build QEMU this just installs the
7 # to build and run linux-user tests on GitLab
18 apt build-dep -yy qemu
20 # Add extra build tools and as many cross compilers as we can for testing
29 ninja-build \
|
| /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
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::
24 mkdir build
[all …]
|
| H A D | index-build.rst | 4 Details about how QEMU's build system works. You will need to understand
5 some of the basics if you are adding new files and targets to the build.
10 build-system
11 build-environment
|
| H A D | build-environment.rst | 2 .. _setup-build-env:
4 Setup build environment
20 Note: Installing dependencies using your package manager build dependencies may
42 sudo apt update && sudo apt build-dep qemu
52 brew update && brew install $(brew deps --include-build qemu)
71 MSYS2 package manager does not offer a built-in way to install build
96 build QEMU in MSYS2 itself.
|
| /qemu/tests/vm/ |
| H A D | Makefile.include | 12 .PHONY: vm-build-all vm-clean-all
86 vm-build-all: $(addprefix vm-build-, $(IMAGES))
100 $(if $(QEMU_LOCAL),--build-path $(BUILD_DIR)) \
106 --build-image $@, \
110 vm-build-%: $(IMAGES_DIR)/%.img $(VM_VENV)
117 $(if $(QEMU_LOCAL),--build-path $(BUILD_DIR)) \
121 $(if $(BUILD_TARGET),--build-target $(BUILD_TARGET)) \
123 --build-qemu $(SRC_PATH) -- \
141 $(if $(QEMU_LOCAL),--build-path $(BUILD_DIR)) \
|
| /qemu/tests/uefi-test-tools/ |
| H A D | uefi-test-build.config | 7 [build.arm]
17 [build.aarch64]
27 [build.loongarch64]
37 [build.riscv64]
47 [build.ia32]
57 [build.x64]
|
| /qemu/tests/ |
| H A D | Makefile.include | 40 BUILD_TCG_TARGET_RULES=$(patsubst %,build-tcg-tests-%, $(TCG_TESTS_TARGETS))
48 .PHONY: $(TCG_TESTS_TARGETS:%=build-tcg-tests-%)
49 $(TCG_TESTS_TARGETS:%=build-tcg-tests-%): build-tcg-tests-%: $(BUILD_DIR)/tests/tcg/config-%.mak
55 $(TCG_TESTS_TARGETS:%=run-tcg-tests-%): run-tcg-tests-%: build-tcg-tests-%
72 .PHONY: build-tcg
73 build-tcg: $(BUILD_TCG_TARGET_RULES)
120 check-build: run-ninja
|
| /qemu/ |
| H A D | Makefile | 31 docker docker-% lcitool-refresh vm-help vm-test vm-build-%
54 $(error This is an out of tree build but your source tree ($(SRC_PATH)) \
55 seems to have been used for an in-tree build. You can fix this by running \
71 ifeq ($(wildcard build.ninja),)
100 Makefile.ninja: build.ninja
104 echo 'build-files = \'; \
|
| /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
32 You can find how to install build dependencies for different systems on the
33 :ref:`setup-build-env` page.
60 Other host architectures are not supported. It is possible to build QEMU system
93 Some build dependencies may follow less conservative rules:
106 Python build dependencies
107 Some of QEMU's build dependencies are written in Python. Usually these
111 Package Index (PyPI) via ``pip``, in order to build QEMU.
[all …]
|
| /qemu/rust/ |
| H A D | .gitignore | 1 # Ignore any cargo development build artifacts; for qemu-wide builds, all build
2 # artifacts will go to the meson build directory.
|
| /qemu/tests/docker/ |
| H A D | Makefile.include | 41 DOCKER_BUILDKIT=1 $(RUNC) build \
45 --build-arg BUILDKIT_INLINE_CACHE=1 \
47 --build-arg USER=$(USER) \
48 --build-arg UID=$(UID)) \
65 $(DOCKER_SCRIPT) build -t qemu/debian-$* -f $< \
97 $(DOCKER_SCRIPT) build -t qemu/$1 -f $< \
100 $(DOCKER_FILES_DIR)/$1.d/build-toolchain.sh, \
114 $(DOCKER_FILES_DIR)/debian-microblaze-cross.d/build-toolchain.sh
|
| H A D | test-fuzz | 20 mkdir build-oss-fuzz
22 env CC="clang" CXX="clang++" CFLAGS="-fsanitize=address" ./scripts/oss-fuzz/build.sh
24 for fuzzer in $(find ./build-oss-fuzz/DEST_DIR/ -executable -type f | grep -v slirp); do
|
| H A D | test-misc | 17 requires_binary sphinx-build-3 sphinx-build
|
| /qemu/docs/devel/testing/ |
| H A D | main.rst | 9 tests you can run ``make check-help`` from either the source or build
13 the meson build system so can be run directly from the build tree,
51 Before running tests, it is best to build QEMU programs first. Some tests
83 3. Add the test to ``tests/unit/meson.build``. The unit tests are listed in a
150 the build in the meson.build file.
200 ``tests/qemu-iotests`` directory under the build directory, and run ``./check``
334 # ci - tests to run on build
368 build and test QEMU in predefined and widely accessible Linux
432 make docker-test-build@debian
435 is downloaded and initialized automatically), in which the ``test-build`` job
[all …]
|
| /qemu/scripts/coverity-scan/ |
| H A D | run-coverity-scan | 120 tests/docker/docker.py --engine ${DOCKER_ENGINE} build \
409 rm -rf +build
410 mkdir +build
411 cd +build
436 cov-build --dir cov-int $COVERITY_BUILD_CMD
|
| /qemu/hw/loongarch/ |
| H A D | meson.build | 7 'virt-fdt-build.c',
9 loongarch_ss.add(when: 'CONFIG_ACPI', if_true: files('virt-acpi-build.c'))
|
| /qemu/rust/qemu-api/ |
| H A D | README.md | 5 The C bindings can be generated with `bindgen`, using this build target:
13 Common Cargo tasks can be performed from the QEMU build directory
|