| /third_party/rust/crates/rustix/.github/workflows/ |
| D | test-users.yml | 10 runs-on: ${{ matrix.os }}
15 …build: [ubuntu, i686-linux, aarch64-linux, powerpc64le-linux, riscv64-linux, mipsel-linux, mips64e…
17 - build: ubuntu
18 os: ubuntu-latest
20 - build: i686-linux
21 os: ubuntu-latest
23 target: i686-unknown-linux-gnu
24 gcc_package: gcc-i686-linux-gnu
25 gcc: i686-linux-gnu-gcc
26 libc_package: libc-dev-i386-cross
[all …]
|
| D | main.yml | 6 - main
13 runs-on: ubuntu-latest
15 - uses: actions/checkout@v3
18 - uses: ./.github/actions/install-rust
21 - run: cargo fmt --all -- --check
25 runs-on: ${{ matrix.os }}
28 build: [stable, nightly, 1.48]
30 - build: stable
31 os: ubuntu-latest
33 - build: nightly
[all …]
|
| /third_party/libuv/.github/workflows/ |
| D | CI-unix.yml | 1 name: CI-unix
6 - '**'
7 - '!docs/**'
8 - '!src/win/**'
9 - '!.**'
10 - '.github/workflows/CI-unix.yml'
13 - v[0-9].*
14 - master
17 build-linux:
18 runs-on: ubuntu-latest
[all …]
|
| /third_party/toybox/scripts/ |
| D | mkroot.sh | 4 [ -z "$NOCLEAR" ] &&
5 exec env -i NOCLEAR=1 HOME="$HOME" PATH="$PATH" LINUX="$LINUX" \
9 while [ $# -ne 0 ]
18 if [ -z "$CROSS_COMPILE" ]
21 if ! cc --static -xc - -o /dev/null <<< "int main(void) {return 0;}"
29 [ -z "$CROSS_SHORT" ] && CROSS_SHORT="${CROSS_BASE/-*/}"
31 if [ -z "$CROSS_PATH" ]
33 echo "no ${CROSS_COMPILE}cc in path" >&2
40 [ -z "$BUILD" ] && BUILD="$TOP/build"
41 [ -z "$AIRLOCK" ] && AIRLOCK="$TOP/airlock"
[all …]
|
| /third_party/rust/rust/src/ci/docker/host-x86_64/test-various/uefi_qemu_test/ |
| D | run.py | 11 TARGET_AARCH64 = 'aarch64-unknown-uefi'
12 TARGET_I686 = 'i686-unknown-uefi'
13 TARGET_X86_64 = 'x86_64-unknown-uefi'
17 cmd = [str(p) for p in cmd]
32 qemu = 'qemu-system-aarch64'
34 cpu = 'cortex-a72'
40 # The i686 target intentionally uses 64-bit qemu; the important
41 # difference is that the OVMF code provides a 32-bit environment.
42 qemu = 'qemu-system-x86_64'
50 qemu = 'qemu-system-x86_64'
[all …]
|
| /third_party/rust/rust/src/doc/rustc/src/platform-support/ |
| D | armv7-unknown-linux-uclibceabihf.md | 1 # armv7-unknown-linux-uclibceabihf
5 This tier supports the ARMv7 processor running a Linux kernel and uClibc-ng standard library. It p…
13 …ss toolchain. You can find suitable pre-built toolchains at [bootlin](https://toolchains.bootlin.…
21 …ootlin.com/downloads/releases/toolchains/armv7-eabihf/tarballs/armv7-eabihf--uclibc--bleeding-edge…
25 The target can be built by enabling it for a `rustc` build, by placing the following in `config.tom…
28 [build]
29 target = ["armv7-unknown-linux-uclibceabihf"]
32 [target.armv7-unknown-linux-uclibceabihf]
34 cc = "/TOOLCHAIN_PATH/bin/arm-buildroot-linux-uclibcgnueabihf-gcc"
37 ### Build subsection
[all …]
|
| D | m68k-unknown-linux-gnu.md | 1 # m68k-unknown-linux-gnu
14 This target requires a Linux/m68k build environment for cross-compilation which
15 is available on Debian and Debian-based systems, openSUSE and other distributions.
17 On Debian, it should be sufficient to install a g++ cross-compiler for the m68k
18 architecture which will automatically pull in additional dependencies such as
22 # apt install g++-m68k-linux-gnu
25 Binaries can be run using QEMU user emulation. On Debian-based systems, it should be
26 sufficient to install the package `qemu-user-static` to be able to run simple static
30 # apt install qemu-user-static
37 # apt install debootstrap debian-ports-archive-keyring
[all …]
|
| D | armv7-unknown-linux-uclibceabi.md | 1 # `armv7-unknown-linux-uclibceabi`
5 …Us and uses the uclibc-ng standard library. This is a common configuration on many consumer router…
19 …build a `'C'` cross toolchain that targets ARMv7 softfloat and that uses the uclibc-ng standard li…
21 …-toolchain) is a sample toolchain that is built using [buildroot](https://buildroot.org/). It uses…
25 [rust-bootstrap-armv7-unknown-linux-uclibceabi](https://github.com/lancethepants/rust-bootstrap-arm…
31 [build]
32 build-stage = 2
33 target = ["armv7-unknown-linux-uclibceabi"]
35 [target.armv7-unknown-linux-uclibceabi]
36 cc = "/path/to/arm-unknown-linux-uclibcgnueabi-gcc"
[all …]
|
| D | unknown-uefi.md | 1 # `*-unknown-uefi`
10 - `aarch64-unknown-uefi`
11 - `i686-unknown-uefi`
12 - `x86_64-unknown-uefi`
16 - David Rheinsberg ([@dvdhrm](https://github.com/dvdhrm))
17 - Nicholas Bishop ([@nicholasbishop](https://github.com/nicholasbishop))
21 All UEFI targets can be used as `no-std` environments via cross-compilation.
26 minor differences. Therefore, cross-compiling for UEFI works with the same
27 tools as cross-compiling for Windows. The target binaries are PE32+ encoded,
30 `efiapi` Rust calling-convention chooses the right ABI for the target platform
[all …]
|
| /third_party/rust/rust/src/ci/docker/host-x86_64/disabled/riscv64gc-linux/ |
| D | Dockerfile | 1 # based on armhf-gnu/Dockerfile
4 RUN echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections
5 RUN apt-get update -y && apt-get install -y --no-install-recommends \
8 ca-certificates \
12 debian-ports-archive-keyring \
16 gcc-riscv64-linux-gnu \
18 g++-riscv64-linux-gnu \
20 libc6-dev \
21 libc6-dev-riscv64-cross \
23 ninja-build \
[all …]
|
| /third_party/rust/rust/src/ci/docker/host-x86_64/armhf-gnu/ |
| D | Dockerfile | 3 RUN apt-get update -y && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends \
6 ca-certificates \
12 g++-arm-linux-gnueabihf \
14 libc6-dev \
15 libc6-dev-armhf-cross \
17 ninja-build \
19 qemu-system-arm \
20 xz-utils
23 CROSS_COMPILE=arm-linux-gnueabihf-
25 WORKDIR /build
[all …]
|
| /third_party/rust/crates/libc/ci/ |
| D | README.md | 4 serve as a guide through the sea of scripts in this directory and elsewhere in
8 in the `ci` directory how we run CI now.
12 First up, let's talk about the files in this directory:
14 * `run-docker.sh` - a shell script run by most builders, it will execute
17 * `run.sh` - the actual script which runs tests for a particular architecture.
19 * `dox.sh` - build the documentation of the crate and publish it to gh-pages.
24 for running tests. You can find tested triples in [Actions config] or [Cirrus config].
28 the right installer). The Intel Linux/OSX builds are similar in that we just
34 * Android runs in a [docker image][android-docker] with an emulator, the NDK,
35 and the SDK already set up. The entire build happens within the docker image.
[all …]
|
| D | run.sh | 6 set -ex
8 MIRRORS_URL="https://ci-mirrors.rust-lang.org/libc"
12 # If we're going to run tests inside of a qemu image, then we don't need any of
18 if [ "$QEMU" != "" ]; then
19 tmpdir=/tmp/qemu-img-creation
20 mkdir -p "${tmpdir}"
22 if [ -z "${QEMU#*.gz}" ]; then
24 qemufile="$(echo "${QEMU%.gz}" | sed 's/\//__/g')"
25 if [ ! -f "${tmpdir}/${qemufile}" ]; then
26 curl --retry 5 "${MIRRORS_URL}/${QEMU}" | \
[all …]
|
| /third_party/lz4/.circleci/ |
| D | config.yml | 2 # It should include any build commands you had along with commands that CircleCI
4 # comments in this file to understand the structure of CircleCI 2.0, as the idiom
5 # for configuration has changed substantially in 2.0 to allow arbitrary jobs rather
6 # than the prescribed lifecycle of 1.0. In general, we recommend using this generated
7 # configuration as a reference rather than using it in production, though in most
11 build:
13 # Parallelism is broken in this file : it just plays the same tests twice.
15 # In the meantime, set it to 1.
17 shell: /bin/bash --login
19 …t or see https://circleci.com/docs/2.0/env-vars/#interpolating-environment-variables-to-set-other-…
[all …]
|
| /third_party/rust/rust/src/ci/docker/host-x86_64/test-various/ |
| D | Dockerfile | 3 RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends \
4 clang-11 \
7 ninja-build \
10 ca-certificates \
16 libssl-dev \
17 pkg-config \
18 xz-utils \
22 qemu-efi-aarch64 \
23 qemu-system-arm \
24 qemu-system-x86 \
[all …]
|
| /third_party/rust/rust/compiler/rustc_codegen_cranelift/.github/workflows/ |
| D | main.yml | 4 - push
5 - pull_request
9 runs-on: ubuntu-latest
10 timeout-minutes: 10
13 - uses: actions/checkout@v3
15 - name: Install rustfmt
19 - name: Rustfmt
21 cargo fmt --check
22 rustfmt --check build_system/main.rs
23 rustfmt --check example/*
[all …]
|
| /third_party/rust/rust/src/bootstrap/ |
| D | configure.py | 3 # ignore-tidy-linelength
35 o("docs", "build.docs", "build standard library documentation")
36 o("compiler-docs", "build.compiler-docs", "build compiler documentation")
37 o("optimize-tests", "rust.optimize-tests", "build tests with optimizations")
38 o("verbose-tests", "rust.verbose-tests", "enable verbose output when running tests")
41 o("local-rust", None, "use an installed rustc rather than downloading a snapshot")
42 v("local-rust-root", None, "set prefix for local rust binary")
43 …"local-rebuild", "build.local-rebuild", "assume local-rust matches the current version, for rebuil…
44 o("llvm-static-stdcpp", "llvm.static-libstdcpp", "statically link to libstdc++ for LLVM")
45 o("llvm-link-shared", "llvm.link-shared", "prefer shared linking to LLVM (llvm-config --link-shared…
[all …]
|
| /third_party/grpc/tools/dockerfile/ |
| D | README.md | 8 exception of `third_party/rake-compiler-dock` docker images).
15 For each dockerfile (which is identified by the directory in which is it located),
26 us-docker.pkg.dev/grpc-testing/testing-images-public/cxx_debian11_x64:[CURRENT_CHECKSUM]@sha256:[CU…
33 The authoritative version of docker images we use for testing is stored in artifact registry,
34 under the repository `us-docker.pkg.dev/grpc-testing/testing-images-public`.
39 If you haven't configured authentication in Docker for us-docker.pkg.dev previously, run:
42 gcloud auth configure-docker us-docker.pkg.dev
48 that are already in artifact registry)
51 # Install qemu, binformat, and configure binfmt interpreters
52 sudo apt-get install binfmt-support qemu-user-static
[all …]
|
| /third_party/toybox/ |
| D | README | 1 Toybox: all-in-one Linux command line.
3 --- Getting started
10 the parent directory), and you can run a program that isn't in the $PATH by
13 wget http://landley.net/toybox/bin/toybox-x86_64
14 chmod +x toybox-x86_64
15 ./toybox-x86_64 echo hello world
17 --- Building toybox
19 Type "make help" for build instructions.
30 LDFLAGS="--static" CROSS_COMPILE=armv5l- make defconfig toybox
34 that control the toybox build; if you export any of these variables into your
[all …]
|
| /third_party/rust/crates/nix/ |
| D | .cirrus.yml | 6 # Build by default; don't just check
7 BUILD: build
8 CLIPPYFLAGS: -D warnings -A unknown-lints
9 RUSTFLAGS: -D warnings
10 RUSTDOCFLAGS: -D warnings
15 # Tests that don't require executing the build binaries
16 build: &BUILD
18 - . $HOME/.cargo/env || true
19 - $TOOL -Vv
20 - rustc -Vv
[all …]
|
| /third_party/benchmark/.github/workflows/ |
| D | wheels.yml | 1 name: Build and upload Python wheels
7 - published
11 name: Build source distribution
12 runs-on: ubuntu-latest
14 - name: Check out repo
17 - name: Install Python 3.9
18 uses: actions/setup-python@v2
20 python-version: 3.9
22 - name: Build and check sdist
25 - name: Upload sdist
[all …]
|
| /third_party/libinput/ |
| D | .gitlab-ci.yml | 9 # To change the gitlab CI, edit .gitlab-ci/ci.template and/or .gitlab-ci/config.yaml
10 # and run ci-fairy generate-template. For details, see
11 # https://freedesktop.pages.freedesktop.org/ci-templates/ci-fairy.html#templating-gitlab-ci-yml
14 # - we really want to run dnf/apt/... only once, updating on the test runner for
18 # This is handled by the ci-templates, ensuring containers are only rebuilt
21 # - GitLab only allows one script: set per job but we have a bunch of commands
22 # we need to re-run for each build (meson && ninja && etc). YAML cannot merge
27 # MESON_ARGS=-Denable-something=true
28 # NINJA_ARGS=dist ... to run 'ninja -C builddir dist'
29 # Note that you cannot use scripts: in any target if you expect default_build
[all …]
|
| /third_party/openssl/ |
| D | NOTES-ANDROID.md | 5 -------------------
15 -------------
17 Android is a cross-compiled target and you can't rely on `./Configure`
19 target explicitly; there are `android-arm`, `android-arm64`, `android-mips`,
20 `android-mip64`, `android-x86` and `android-x86_64` (`*MIPS` targets are no
23 Do not pass --cross-compile-prefix (as you might be tempted), as it
25 you still need to know the prefix to extend your PATH, in order to
30 to point at the `NDK` directory. If you're using a side-by-side NDK the path
31 will look something like `/some/where/android-sdk/ndk/<ver>`, and for a
32 standalone NDK the path will be something like `/some/where/android-ndk-<ver>`.
[all …]
|
| /third_party/brotli/ |
| D | CMakeLists.txt | 2 # - Ubuntu 20.04 LTS : 3.16.3
3 # - Solaris 11.4 SRU 15 : 3.15
8 # This policy is set because we can't provide "VERSION" in "project" command.
9 # Use `cmake --help-policy CMP0048` for more information.
13 option(BUILD_SHARED_LIBS "Build shared libraries" ON)
16 message(STATUS "Setting build type to Release as none was specified.")
17 set(CMAKE_BUILD_TYPE "Release" CACHE STRING "Choose the type of build." FORCE)
19 message(STATUS "Build type is '${CMAKE_BUILD_TYPE}'")
30 message("-- Compiler is EMSCRIPTEN")
32 message("-- Compiler is not EMSCRIPTEN")
[all …]
|
| /third_party/rust/rust/compiler/rustc_codegen_cranelift/build_system/ |
| D | utils.rs | 23 "aarch64-unknown-linux-gnu" => { in set_cross_linker_and_runner()
24 // We are cross-compiling for aarch64. Use the correct linker and run tests in qemu. in set_cross_linker_and_runner()
25 self.rustflags += " -Clinker=aarch64-linux-gnu-gcc"; in set_cross_linker_and_runner()
26 self.rustdocflags += " -Clinker=aarch64-linux-gnu-gcc"; in set_cross_linker_and_runner()
28 "qemu-aarch64".to_owned(), in set_cross_linker_and_runner()
29 "-L".to_owned(), in set_cross_linker_and_runner()
30 "/usr/aarch64-linux-gnu".to_owned(), in set_cross_linker_and_runner()
33 "s390x-unknown-linux-gnu" => { in set_cross_linker_and_runner()
34 // We are cross-compiling for s390x. Use the correct linker and run tests in qemu. in set_cross_linker_and_runner()
35 self.rustflags += " -Clinker=s390x-linux-gnu-gcc"; in set_cross_linker_and_runner()
[all …]
|