Searched +full:build +full:- +full:in +full:- +full:qemu (Results 1 – 25 of 60) sorted by relevance
123
| /third_party/rust/crates/rustix/.github/workflows/ |
| 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 …]
|
| 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 …]
|
| /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/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/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 RUSTFLAGS: -D warnings
9 RUSTDOCFLAGS: -D warnings
15 # Tests that don't require executing the build binaries
16 build: &BUILD
18 - . $HOME/.cargo/env || true
19 - $TOOL +$TOOLCHAIN -Vv
20 - rustc +$TOOLCHAIN -Vv
21 - $TOOL +$TOOLCHAIN $BUILD $ZFLAGS --target $TARGET --all-targets
[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/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/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/skia/third_party/externals/brotli/ |
| D | CMakeLists.txt | 10 message(STATUS "Setting build type to Release as none was specified.")
11 set(CMAKE_BUILD_TYPE "Release" CACHE STRING "Choose the type of build." FORCE)
13 message(STATUS "Build type is '${CMAKE_BUILD_TYPE}'")
24 message("-- Compiler is EMSCRIPTEN")
26 message("-- Compiler is not EMSCRIPTEN")
29 # If Brotli is being bundled in another project, we don't want to
32 # set it to OFF in your project before you add_subdirectory(brotli).
36 # depending on whether or not we are the top-level project.
49 # (i.e., config.h), but in this case we parse them from
58 string(SUBSTRING "${_tail}" 1 -1 _tail)
[all …]
|
| /third_party/jerryscript/ |
| D | .travis.yml | 7 # Default job task: run tests as defined in the $OPT environment variable.
8 # Jobs can redefine the 'script' stage in the matrix below.
9 script: tools/run-tests.py $OPTS
11 # All the job definitions in the matrix.
14 - name: "Checks"
16 …- tools/run-tests.py --check-signed-off=travis --check-doxygen --check-vera --check-license --chec…
17 - travis_wait 40 tools/run-tests.py --check-cppcheck
22 - name: "Linux/x86-64 Build, Correctness & Debugger Tests"
24 - OPTS="--quiet --jerry-tests --jerry-test-suite --jerry-debugger"
26 - name: "Linux/x86 (cpointer-32bit) Build & Correctness Tests"
[all …]
|
| /third_party/mesa3d/docs/drivers/ |
| D | venus.rst | 1 Virtio-GPU Venus
4 Venus is a Virtio-GPU protocol for Vulkan command serialization. The protocol
5 definition and codegen are hosted at `venus-protocol
6 <https://gitlab.freedesktop.org/olv/venus-protocol>`__. The renderer is
14 ------------
18 - Vulkan 1.1
19 - ``VK_EXT_external_memory_dma_buf``
20 - ``VK_EXT_image_drm_format_modifier``
21 - ``VK_EXT_queue_family_foreign``
23 from the host driver. However, it violates the spec in some places currently
[all …]
|
| /third_party/optimized-routines/ |
| D | README | 2 ----------------------
6 license, at the user’s election, as reflected in the LICENSE file.
8 to sign an Assignment Agreement, please follow the instructions in
9 contributor-agreement.pdf. This is needed so upstreaming code
11 contribution requirements are documented in README.contributors of
19 build/ - build directory (created by make).
20 math/ - math subproject sources.
21 math/include/ - math library public headers.
22 math/test/ - math test and benchmark related sources.
23 math/tools/ - tools used for designing the algorithms.
[all …]
|
| D | config.mk.dist | 3 # Copyright (c) 2018-2020, Arm Limited.
4 # SPDX-License-Identifier: MIT OR Apache-2.0 WITH LLVM-exception
6 # Subprojects to build
13 #CROSS_COMPILE = aarch64-none-linux-gnu-
17 CFLAGS = -std=c99 -pipe -O3
18 CFLAGS += -Wall -Wno-missing-braces
19 CFLAGS += -Werror=implicit-function-declaration
23 HOST_CFLAGS = -std=c99 -O2
24 HOST_CFLAGS += -Wall -Wno-unused-function
27 HOST_CFLAGS += -g
[all …]
|
| /third_party/jerryscript/targets/zephyr/ |
| D | README.md | 8 ### How to build
14 Assume `harmony` as the path to the projects to build.
22 + zephyr-project
38 Application" section in the doc above and check that you can flash your
41 Remember to source the Zephyr environment as explained in the zephyr documenation:
44 cd zephyr-project
45 source zephyr-env.sh
51 #### 3. Build JerryScript for Zephyr
53 The easiest way is to build and run on a QEMU emulator:
58 make -f ./targets/zephyr/Makefile.zephyr BOARD=qemu_x86 run
[all …]
|
| /third_party/toybox/www/ |
| D | faq.html | 2 <!--#include file="header.html" -->
16 <li><h2><a href="#b_links">What are those /b/number links in the git log?</a></h2></li>
19 <li><h2><a href="#dotslash">What's this ./ on the front of commands in your examples?</a></h2></li>
26 <!-- get binaries -->
30 <li><h2><a href="#mkroot">How do I build a working Linux system with toybox?</a></h2></li>
35 <p>A: Toybox started back in 2006 when I (Rob Landley)
37 and <a href=http://landley.net/notes-2006.html#28-09-2006>started over from
39 <a href=http://lists.busybox.net/pipermail/busybox/2006-September/058617.html>protracted licensing …
42 <a href=http://landley.net/notes-2011.html#13-11-2011>relaunched</a>
43 in November 2011 with a new goal to make Android
[all …]
|
| D | about.html | 2 <!--#include file="header.html" -->
7 a single <a href=license.html>BSD-licensed</a> executable. It's simple, small, fast, and reasonably
8 standards-compliant (<a href=http://opengroup.org/onlinepubs/9699919799>POSIX-2008</a> and <a href=…
11 <a href=http://landley.net/aboriginal/about.html#selfhost>self-hosting</a>
13 build an installable Android Open Source Project image
16 (<a href=http://landley.net/talks/celf-2013.txt>outline</a>,
19 began shipping toybox in Android Marshmallow in 2015.</p>
26 under the result. In theory, this should only require four packages:
27 1) a set of posix-ish command line utilities,
28 2) a compiler<a name="1_back"></a><sup><font size=-3><a href=#1>[1]</a></font></sup>,
[all …]
|
| /third_party/libbpf/ |
| D | .travis.yml | 5 - docker
9 - PROJECT_NAME='libbpf'
10 - AUTHOR_EMAIL="$(git log -1 --pretty=\"%aE\")"
11 - REPO_ROOT="$TRAVIS_BUILD_DIR"
12 - CI_ROOT="$REPO_ROOT/travis-ci"
13 - VMTEST_ROOT="$CI_ROOT/vmtest"
18 - qemu-kvm
19 - zstd
20 - binutils-dev
21 - elfutils
[all …]
|
| /third_party/libuv/ |
| D | CMakeLists.txt | 27 option(LIBUV_BUILD_SHARED "Build shared lib" ON)
30 "Build the unit tests when BUILD_TESTING is enabled and we are the root project" ON
33 "Build the benchmarks when building unit tests and we are the root project" ON
36 # Qemu Build
37 option(QEMU "build for qemu" OFF) option
38 if(QEMU)
49 message(SEND_ERROR "MemorySanitizer requires clang. Try again with -DCMAKE_C_COMPILER=clang")
55 set (CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -fno-omit-frame-pointer -fsanitize=address")
56 …set (CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS} -fno-omit-frame-pointer -fsanitize=ad…
57 …set (CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -fno-omit-frame-pointer -fsanitize=address")
[all …]
|
| /third_party/flatbuffers/tests/ |
| D | RustTest.sh | 2 set -e
7 # you may not use this file except in compliance with the License.
10 # http://www.apache.org/licenses/LICENSE-2.0
12 # Unless required by applicable law or agreed to in writing, software
18 if [[ "$1" == "mips-unknown-linux-gnu" ]]; then
19 TARGET_FLAG="--target mips-unknown-linux-gnu"
20 export CARGO_TARGET_MIPS_UNKNOWN_LINUX_GNU_LINKER=mips-linux-gnu-gcc
21 export CARGO_TARGET_MIPS_UNKNOWN_LINUX_GNU_RUNNER="qemu-mips -L /usr/mips-linux-gnu"
35 cargo run $TARGET_FLAG -- --quiet
40 rustup component add rust-src --toolchain nightly
[all …]
|
| /third_party/PyYAML/.github/workflows/ |
| D | manual_artifact_build.yaml | 1 ---
2 # This is the actual artifact build/release workflow. This workflow exists temporarily
4 name: Manual Artifact Build
19 runs-on: ubuntu-latest
21 - name: Checkout PyYAML
24 - name: Install a python
25 uses: actions/setup-python@v2
27 python-version: 3.x
29 - name: Build sdist
34 python -V
[all …]
|
| D | ci.yaml | 1 ---
2 # This is the CI workflow (not the artifact build/release workflow). The workflows
21 runs-on: ubuntu-latest
23 - name: Checkout PyYAML
26 - name: Install a python
27 uses: actions/setup-python@v2
29 python-version: 3.x
31 - name: Build sdist
36 python -V
37 python -m pip install build
[all …]
|
123