Searched +full:cmake +full:- +full:gcc (Results 1 – 25 of 513) sorted by relevance
12345678910>>...21
| /external/rust/crates/libz-sys/src/zlib-ng/.github/workflows/ |
| D | cmake.yml | 1 name: CI CMake
4 ci-cmake:
6 runs-on: ${{ matrix.os }}
8 fail-fast: false
11 Ubuntu GCC,
12 Ubuntu GCC OSB -O1,
13 Ubuntu GCC Link Zlib,
14 Ubuntu GCC No AVX2,
15 Ubuntu GCC No SSE2,
16 Ubuntu GCC No SSE4,
[all …]
|
| D | pkgcheck.yml | 4 ci-pkgcheck:
6 runs-on: ${{ matrix.os }}
8 fail-fast: false
11 Ubuntu GCC,
12 Ubuntu GCC -m32,
13 Ubuntu GCC ARM HF,
14 Ubuntu GCC AARCH64,
15 Ubuntu GCC PPC,
16 Ubuntu GCC PPC64LE,
20 - name: Ubuntu GCC
[all …]
|
| /external/flac/.github/workflows/ |
| D | action.yml | 11 ubuntu-latest-gcc-autotools,
12 ubuntu-latest-clang-autotools,
13 ubuntu-latest-gcc-cmake,
14 ubuntu-latest-clang-cmake,
15 macos-latest-clang-autotools,
16 macos-latest-clang-cmake,
17 ubuntu-latest-gcc-autotools-64-bit-words,
18 ubuntu-latest-clang-autotools-64-bit-words,
19 ubuntu-latest-gcc-cmake-64-bit-words,
20 ubuntu-latest-clang-cmake-64-bit-words,
[all …]
|
| /external/swiftshader/tests/kokoro/gcp_ubuntu/ |
| D | continuous.sh | 5 set -e # Fail on any error.
6 set -x # Display commands being run.
8 # Update CMake
9 sudo aptitude purge -yq cmake
10 wget -O - https://apt.kitware.com/keys/kitware-archive-latest.asc 2>/dev/null | sudo apt-key add -
11 sudo apt-add-repository 'deb https://apt.kitware.com/ubuntu/ xenial main'
12 sudo aptitude update -yq
13 sudo aptitude install -yq cmake
14 cmake --version
16 # Specify we want to build with GCC 9
[all …]
|
| /external/brotli/ |
| D | .travis.yml | 5 - master
9 ## Linux builds using various versions of GCC.
11 - os: linux
12 env: BUILD_SYSTEM=cmake C_COMPILER=gcc-7 CXX_COMPILER=g++-7
16 - ubuntu-toolchain-r-test
18 - gcc-7
19 - g++-7
20 - os: linux
21 env: BUILD_SYSTEM=cmake C_COMPILER=gcc-4.4 CXX_COMPILER=g++-4.4
25 - ubuntu-toolchain-r-test
[all …]
|
| /external/llvm-project/flang/ |
| D | .drone.star | 4 "name": "%s-clang" % arch,
10 …"apt-get update && apt-get install -y clang-8 cmake ninja-build lld-8 llvm-8-dev libc++-8-dev libc…
11 … "git clone --depth=1 -b f18 https://github.com/flang-compiler/f18-llvm-project.git llvm-project",
12 "mkdir llvm-project/build && cd llvm-project/build",
13 …-8 CXX=clang++-8 CXXFLAGS="-stdlib=libc++" LDFLAGS="-fuse-ld=lld" cmake -GNinja -DCMAKE_BUILD_TYPE…
17 …-8 CXX=clang++-8 CXXFLAGS="-UNDEBUG -stdlib=libc++" LDFLAGS="-fuse-ld=lld" cmake -GNinja -DCMAKE_B…
18 "ninja -j8",
19 "ctest --output-on-failure -j24",
20 "ninja check-all",
27 def gcc(arch):
[all …]
|
| /external/libpcap/ |
| D | .travis.yml | 4 # Try building on these 4 architectures; all are 64-bit, and all but
5 # "s390x", a/k/a z/Architecture, are little-endian.
8 - amd64
9 - ppc64le
10 - s390x
11 - arm64
14 - linux
15 - osx
20 - gcc
21 - clang
[all …]
|
| /external/rust/crates/libz-sys/src/zlib-ng/test/ |
| D | pkgcheck.sh | 5 Usage: sh test/pkgcheck.sh [--zlib-compat]
8 If --zlib-compat, tests with zlib compatible builds.
12 $ sudo apt install ninja-build diffoscope gcc-multilib
13 $ export CMAKE_ARGS="-DCMAKE_C_FLAGS=-m32" CFLAGS=-m32 LDFLAGS=-m32
16 To cross-build, install the appropriate qemu and gcc packages,
17 and set the environment variables used by configure or cmake.
21 $ sudo apt install ninja-build diffoscope qemu gcc-arm-linux-gnueabihf libc6-dev-armhf-cross
22 $ export CHOST=arm-linux-gnueabihf
23 $ export CMAKE_ARGS="-DCMAKE_TOOLCHAIN_FILE=cmake/toolchain-arm.cmake -DCMAKE_C_COMPILER_TARGET=${C…
26 $ sudo apt install ninja-build diffoscope qemu gcc-aarch64-linux-gnu libc6-dev-arm64-cross
[all …]
|
| /external/libxml2/ |
| D | .gitlab-ci.yml | 3 # for libxslt, that's why we need git and libgcrypt-dev.
7 # RUN apt-get update && \
8 # apt-get upgrade -y && \
9 # apt-get install -y --no-install-recommends \
10 # curl git ca-certificates \
11 # autoconf automake libtool pkg-config \
12 # make gcc clang llvm \
13 # zlib1g-dev liblzma-dev libgcrypt-dev \
14 # python-dev python3-dev \
15 # cmake
[all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/guide/ |
| D | build_cmake_arm.md | 1 # Cross compilation TensorFlow Lite with CMake
6 The following instructions have been tested on Ubuntu 16.04.3 64-bit PC (AMD64)
15 You need CMake installed and downloaded TensorFlow source code. Please check
16 [Build TensorFlow Lite with CMake](https://www.tensorflow.org/lite/guide/build_cmake)
29 ldd --version
32 <pre class="tfo-notebook-code-cell-output">
33 ldd (Debian GLIBC 2.28-10) 2.28
42 If your target is ARM 32-bit, there are two ABI available depending on VFP
55 <pre class="tfo-notebook-code-cell-output">
71 [Ubuntu Server 20.04.01 LTS 64-bit](https://ubuntu.com/download/raspberry-pi)
[all …]
|
| /external/libjpeg-turbo/ |
| D | BUILDING.md | 1 Building libjpeg-turbo
6 ------------------
11 - [CMake](http://www.cmake.org) v2.8.12 or later
13 - [NASM](http://www.nasm.us) or [YASM](http://yasm.tortall.net)
14 (if building x86 or x86-64 SIMD extensions)
19 - NOTE: Currently, if it is desirable to hide the SIMD function symbols in
21 libjpeg-turbo, then NASM 2.14 or later or YASM must be used when
22 building libjpeg-turbo.
36 ARCH=`uname -m`
37 rpmbuild --rebuild nasm-{version}.src.rpm
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/third_party/upb/kokoro/ubuntu/ |
| D | build.sh | 3 set -ex
6 if [ -x "$(command -v use_bazel.sh)" ]; then
10 # Verify/query CMake
12 ls -l `which cmake`
13 cmake --version
21 if which gcc; then
22 gcc --version
23 CC=gcc bazel test -c opt --test_output=errors ... -- -benchmarks:benchmark
25 CC=gcc bazel test --test_output=errors ...
26 …CC=gcc bazel test --test_output=errors ... --//:fasttable_enabled=true -- -cmake:test_generated_fi…
[all …]
|
| /external/libsrtp2/ |
| D | .travis.yml | 7 …- secure: "QD09MuUxftXRXtz7ZrB7S0NV/3O9yVhjvIlCSbXN8B87rNSDC8wxMThKMT7iZewnqGk53m+Up19PiMw5ERlHose…
13 - os: linux
15 - TEST="linux (gcc / valgrind)"
19 - ubuntu-toolchain-r-test
21 - gcc-6
22 - valgrind
24 - CC=gcc-6 EXTRA_CFLAGS=-Werror ./configure
25 - make
26 - make runtest
27 - make runtest-valgrind
[all …]
|
| /external/llvm-project/llvm/docs/ |
| D | HowToCrossCompileBuiltinsOnArm.rst | 2 How to Cross Compile Compiler-rt Builtins For Arm
9 of compiler-rt for an Arm target, from an x86_64 Linux machine.
12 apply to other targets supported by compiler-rt. Further contributions for other
22 In this use case we'll be using cmake on a Debian-based Linux system,
23 cross-compiling from an x86_64 host to a hard-float Armv7-A target. We'll be
27 * ``A build of LLVM/clang for the llvm-tools and llvm-config``
29 * ``compiler-rt sources``
30 * ``The qemu-arm user mode emulator``
31 * ``An arm-linux-gnueabihf sysroot``
35 See https://compiler-rt.llvm.org/ for more information about the dependencies
[all …]
|
| D | HowToCrossCompileLLVM.rst | 2 How To Cross-Compile Clang/LLVM using Clang/LLVM
11 For more information on how to use Clang as a cross-compiler,
16 Cross-Compiling from x86_64 to ARM
19 In this use case, we'll be using CMake and Ninja, on a Debian-based Linux
20 system, cross-compiling from an x86_64 host (most Intel and AMD chips
21 nowadays) to a hard-float ARM target (most ARM targets nowadays).
25 * ``cmake``
26 * ``ninja-build`` (from backports in Ubuntu)
27 * ``gcc-4.7-arm-linux-gnueabihf``
28 * ``gcc-4.7-multilib-arm-linux-gnueabihf``
[all …]
|
| D | GettingStarted.rst | 19 C-like languages use the `Clang <https://clang.llvm.org/>`_ front end. This
21 -- and from there into object files, using LLVM.
38 * ``git clone https://github.com/llvm/llvm-project.git``
39 * Or, on windows, ``git clone --config core.autocrlf=false
40 https://github.com/llvm/llvm-project.git``
44 * ``cd llvm-project``
47 * ``cmake -G <generator> [options] ../llvm``
51 * ``Ninja`` --- for generating `Ninja <https://ninja-build.org>`_
53 * ``Unix Makefiles`` --- for generating make-compatible parallel makefiles.
54 * ``Visual Studio`` --- for generating Visual Studio projects and
[all …]
|
| /external/harfbuzz_ng/.circleci/ |
| D | config.yml | 5 macos-10.12.6-aat-fonts:
9 - checkout
10 …- run: HOMEBREW_NO_AUTO_UPDATE=1 brew install wget autoconf automake libtool pkg-config ragel free…
11 - run: ./autogen.sh --with-freetype --with-glib --with-gobject --with-cairo
12 - run: make -j4
13 - run: make check || .ci/fail.sh
15 macos-10.13.6-aat-fonts:
19 - checkout
20 …- run: HOMEBREW_NO_AUTO_UPDATE=1 brew install wget autoconf automake libtool pkg-config ragel free…
21 - run: ./autogen.sh --with-freetype --with-glib --with-gobject --with-cairo
[all …]
|
| /external/python/pybind11/.github/workflows/ |
| D | ci.yml | 8 - master
9 - stable
10 - v*
17 fail-fast: false
19 runs-on: [ubuntu-latest, windows-latest, macos-latest]
21 - 2.7
22 - 3.5
23 - 3.6
24 - 3.9
25 # - 3.10-dev # Re-enable once 3.10.0a5 is released
[all …]
|
| /external/catch2/ |
| D | .travis.yml | 5 - /dev-appveyor.*/
8 - ubuntu-toolchain-r-test
9 - llvm-toolchain-trusty
10 - llvm-toolchain-trusty-3.9
11 - llvm-toolchain-trusty-4.0
12 - llvm-toolchain-xenial-5.0
13 - llvm-toolchain-xenial-6.0
19 - os: linux
24 packages: ['clang-3.5']
25 env: COMPILER='clang++-3.5'
[all …]
|
| /external/llvm/docs/ |
| D | HowToCrossCompileLLVM.rst | 2 How To Cross-Compile Clang/LLVM using Clang/LLVM
11 For more information on how to use Clang as a cross-compiler,
16 Cross-Compiling from x86_64 to ARM
19 In this use case, we'll be using CMake and Ninja, on a Debian-based Linux
20 system, cross-compiling from an x86_64 host (most Intel and AMD chips
21 nowadays) to a hard-float ARM target (most ARM targets nowadays).
25 * ``cmake``
26 * ``ninja-build`` (from backports in Ubuntu)
27 * ``gcc-4.7-arm-linux-gnueabihf``
28 * ``gcc-4.7-multilib-arm-linux-gnueabihf``
[all …]
|
| D | GettingStarted.rst | 46 * ``cd where-you-want-llvm-to-live``
47 * ``svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm``
51 * ``cd where-you-want-llvm-to-live``
53 * ``svn co http://llvm.org/svn/llvm-project/cfe/trunk clang``
55 #. Checkout Compiler-RT (required to build the sanitizers) **[Optional]**:
57 * ``cd where-you-want-llvm-to-live``
59 * ``svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt``
63 * ``cd where-you-want-llvm-to-live``
65 * ``svn co http://llvm.org/svn/llvm-project/openmp/trunk openmp``
69 * ``cd where-you-want-llvm-to-live``
[all …]
|
| /external/libiio/src/ |
| D | appveyor.yml | 14 - Release
17 - echo "Checking out sub-modules..."
18 - git submodule update --init
19 - echo "Downloading deps..."
20 - cd C:\
21 - appveyor DownloadFile http://swdownloads.analog.com/cse/build/libiio-win-deps.zip
22 - 7z x -y "C:\libiio-win-deps.zip"
24 - choco install InnoSetup
25 - set PATH=%PATH%;"C:\Program Files (x86)\Inno Setup 5"
28 - set OLD_PATH=%PATH%
[all …]
|
| /external/parameter-framework/upstream/ |
| D | .travis.yml | 2 - linux
3 - osx
8 # https://docs.travis-ci.com/user/languages/objective-c/#Supported-OS-X-iOS-SDK-versions
15 - PREFIX=$HOME/prefix
16 - MY_CMAKE_OPTIONS="-DCMAKE_PREFIX_PATH=$PREFIX -DCMAKE_INSTALL_PREFIX=$HOME/install"
17 - OSX_CMAKE_OPTIONS="-DBUILD_TESTING=OFF -DPYTHON_BINDINGS=OFF -DCLIENT_SIMULATOR=OFF"
18 - CTEST_OUTPUT_ON_FAILURE=1
19 - LINUX=false
20 - OSX=false
23 - gcc
[all …]
|
| /external/libaom/libaom/ |
| D | README.md | 4 1. [Building the lib and applications](#building-the-library-and-applications)
5 - [Prerequisites](#prerequisites)
6 - [Get the code](#get-the-code)
7 - [Basics](#basic-build)
8 - [Configuration options](#configuration-options)
9 - [Dylib builds](#dylib-builds)
10 - [Debugging](#debugging)
11 - [Cross compiling](#cross-compiling)
12 - [Sanitizer support](#sanitizers)
13 - [MSVC builds](#microsoft-visual-studio-builds)
[all …]
|
| /external/pcre/dist2/doc/html/ |
| D | NON-AUTOTOOLS-BUILD.txt | 2 --------------------------------------
12 Building PCRE2 on Windows with CMake
25 configure/make (autotools) build system, as found in many Unix-like
29 There is also support for CMake, which some users prefer, especially in Windows
30 environments, though it can also be run in Unix-like environments. See the
31 section entitled "Building PCRE2 on Windows with CMake" below.
35 provided for those who build PCRE2 without using "configure" or CMake. If you
36 use "configure" or CMake, the .generic versions are not used.
42 hand". If you are going to use CMake, this section does not apply to you; you
43 can skip ahead to the CMake section.
[all …]
|
12345678910>>...21