Home
last modified time | relevance | path

Searched +full:build +full:- +full:clang (Results 1 – 25 of 1159) sorted by relevance

12345678910>>...47

/external/skia/infra/bots/recipe_modules/build/examples/
Dfull.py2 # Use of this source code is governed by a BSD-style license that can be
8 'build',
23 api.build(checkout_root=checkout_root, out_dir=out_dir)
25 api.build.copy_build_products(out_dir=out_dir, dst=dst)
30 'Build-Debian10-Clang-arm-Release-Android_API26',
31 'Build-Debian10-Clang-arm-Release-Android_ASAN',
32 'Build-Debian10-Clang-arm-OptimizeForSize-Android_NoPatch',
33 'Build-Debian10-Clang-arm-Release-Chromebook_GLES',
34 'Build-Debian10-Clang-arm64-Debug-Android_FrameworkWorkarounds',
35 'Build-Debian10-Clang-arm64-Debug-Android_Graphite_Native_Vulkan',
[all …]
/external/skia/infra/bots/
Djobs.json2 {"name": "BazelBuild-modules_canvaskit-ck_full_webgl2_debug-linux_x64",
5 {"name": "BazelBuild-full_library-enforce_iwyu-linux_x64",
8 {"name": "BazelBuild-skottie_tool_gpu-enforce_iwyu-linux_x64",
11 {"name": "BazelBuild-full_library-release-linux_x64",
14 {"name": "BazelBuild-core-release-linux_x64"},
15 {"name": "BazelBuild-ganesh_gl-release-linux_x64"},
16 {"name": "BazelBuild-all_tests-debug-linux_x64"},
17 {"name": "BazelBuild-all_tests-release-linux_x64",
20 {"name": "BazelBuild-cpu_8888_benchmark_android_test-for_android_arm64_release-linux_x64"},
21 {"name": "BazelBuild-hello_bazel_world_android_test-for_android_arm64_release-linux_x64"},
[all …]
/external/clang/docs/
DHowToSetupToolingForLLVM.rst2 How To Setup Clang Tooling For LLVM
5 Clang Tooling provides infrastructure to write tools that need syntactic
7 of specific tools using this infrastructure (e.g. ``clang-check``). This
8 document provides information on how to set up and use Clang Tooling for
14 Clang Tooling needs a compilation database to figure out specific build
17 invoking clang tools, you can either specify a path to a build directory
18 using a command line parameter ``-p`` or let Clang Tooling find this
20 build using CMake to use clang tools.
22 Setup Clang Tooling Using CMake and Make
25 If you intend to use make to build LLVM, you should have CMake 2.8.6 or
[all …]
DLibTooling.rst5 LibTooling is a library to support writing standalone tools based on Clang.
9 For the information on how to setup Clang Tooling for LLVM see
13 ------------
15 Tools built with LibTooling, like Clang Plugins, run ``FrontendActions`` over
20 In this tutorial, we'll demonstrate the different ways of running Clang's
24 --------------------------------
27 example to unit test parts of the Clang AST, ``runToolOnCode`` is what you
30 .. code-block:: c++
32 #include "clang/Tooling/Tooling.h"
37 EXPECT_TRUE(runToolOnCode(new clang::SyntaxOnlyAction, "class X {};"));
[all …]
DTooling.rst5 Clang provides infrastructure to write tools that need syntactic and semantic
7 the different ways to write clang tools, and their pros and cons.
10 --------
12 `LibClang <http://clang.llvm.org/doxygen/group__CINDEX.html>`_ is a stable high
13 level C interface to clang. When in doubt LibClang is probably the interface
20 * Clang Python Bindings
24 * want to interface with clang from other languages than C++
26 * want powerful high-level abstractions, like iterating through an AST with a
27 cursor, and don't want to learn all the nitty gritty details of Clang's AST.
31 * want full control over the Clang AST
[all …]
/external/eigen/ci/
Dbuild.gitlab-ci.yml1 .build:linux:base:
2 stage: build
5 - apt-get update -y
6 - apt-get install -y --no-install-recommends software-properties-common
7 - add-apt-repository -y ppa:ubuntu-toolchain-r/test
8 - apt-get update
9 - apt-get install --no-install-recommends -y ${EIGEN_CI_CXX_COMPILER}
10 ${EIGEN_CI_CC_COMPILER} cmake ninja-build
12 - mkdir -p ${BUILDDIR} && cd ${BUILDDIR}
13 - CXX=${EIGEN_CI_CXX_COMPILER} CC=${EIGEN_CI_CC_COMPILER} cmake -G
[all …]
DREADME.md3 Eigen's CI infrastructure uses two stages: A `build` stage to build the unit-test
4 suite and a `test` stage to run the unit-tests.
6 ### Build Stage
8 The build stage consists of the following jobs:
11 |------------------------------------------|-----------|----------------|------------|---------|
12 | `build:x86-64:linux:gcc-4.8:cxx11-off` | `x86-64` | `Ubuntu 18.04` | `GCC-4.8` | `Off` |
13 | `build:x86-64:linux:gcc-4.8:cxx11-on` | `x86-64` | `Ubuntu 18.04` | `GCC-4.8` | `On` |
14 | `build:x86-64:linux:gcc-9:cxx11-off` | `x86-64` | `Ubuntu 18.04` | `GCC-9` | `Off` |
15 | `build:x86-64:linux:gcc-9:cxx11-on` | `x86-64` | `Ubuntu 18.04` | `GCC-9` | `On` |
16 | `build:x86-64:linux:gcc-10:cxx11-off` | `x86-64` | `Ubuntu 18.04` | `GCC-10` | `Off` |
[all …]
Dtest.gitlab-ci.yml6 - apt-get update -y
7 - apt-get install -y --no-install-recommends software-properties-common
8 - add-apt-repository -y ppa:ubuntu-toolchain-r/test
9 - apt-get update
10 - apt-get install --no-install-recommends -y ${EIGEN_CI_CXX_COMPILER}
11 ${EIGEN_CI_CC_COMPILER} cmake ninja-build xsltproc
13 - export CXX=${EIGEN_CI_CXX_COMPILER}
14 - export CC=${EIGEN_CI_CC_COMPILER}
15 - cd ${BUILDDIR} && ctest --output-on-failure --no-compress-output
16 --build-no-clean -T test -L ${EIGEN_CI_TEST_LABEL}
[all …]
/external/sdv/vsomeip/third_party/boost/predef/
Dazure-pipelines.yml5 # Copyright Rene Rivera 2019-2020.
10 - develop
11 - master
12 - feature/*
16 - develop
20 AZP_REPO_DIR: $(Build.Repository.LocalPath)
21 AZP_BRANCH: $(Build.SourceBranch)
22 AZP_BRANCH_NAME: $(Build.SourceBranchName)
23 AZP_COMMIT: $(Build.SourceVersion)
24 AZP_REPO: $(Build.Repository.Name)
[all …]
/external/cronet/build/config/siso/
Dclang_mac.star1 # -*- bazel-starlark -*-
3 # Use of this source code is governed by a BSD-style license that can be
5 """Siso configuration for clang/mac."""
15 …"build/mac_files/xcode_binaries/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX…
43 cfg = "buildtools/reclient_cfgs/chromium-browser-clang/rewrapper_mac.cfg"
47 "clang": reproxy_config["platform"],
52 "name": "clang/cxx",
54 "command_prefix": "../../third_party/llvm-build/Release+Asserts/bin/clang++",
55 "platform_ref": "clang",
60 "name": "clang/cc",
[all …]
Dclang_linux.star1 # -*- bazel-starlark -*-
3 # Use of this source code is governed by a BSD-style license that can be
5 """Siso configuration for clang/linux."""
15 "build/linux/debian_bullseye_amd64-sysroot/usr/include:include": {
20 "build/linux/debian_bullseye_amd64-sysroot/usr/lib:headers": {
24 "build/linux/debian_bullseye_i386-sysroot/usr/include:include": {
29 "build/linux/debian_bullseye_i386-sysroot/usr/lib:headers": {
33 …"third_party/android_toolchain/ndk/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include:inclu…
38 …"third_party/android_toolchain/ndk/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/local/include…
57 "build/linux/debian_bullseye_amd64-sysroot:headers": [
[all …]
/external/angle/build/config/siso/
Dclang_mac.star1 # -*- bazel-starlark -*-
3 # Use of this source code is governed by a BSD-style license that can be
5 """Siso configuration for clang/mac."""
31 …"build/mac_files/xcode_binaries/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX…
39 # and need system include dirs when using deps log of -MMD.
41 # TODO: b/323091468 - get sysroot, ios_sdk_path from gn
61 # https://chromium-review.googlesource.com/c/chromium/src/+/5568662
87 cfg = "buildtools/reclient_cfgs/chromium-browser-clang/rewrapper_mac.cfg"
97 "clang": reproxy_config["platform"],
112 "name": "clang/cxx",
[all …]
Dclang_linux.star1 # -*- bazel-starlark -*-
3 # Use of this source code is governed by a BSD-style license that can be
5 """Siso configuration for clang/linux."""
16 # TODO: b/323091468 - Propagate target android ABI and android SDK version
19 "aarch64-linux-android",
20 "arm-linux-androideabi",
21 "i686-linux-android",
22 "riscv64-linux-android",
23 "x86_64-linux-android",
31 "build/linux/debian_bullseye_amd64-sysroot/usr/include:include": {
[all …]
/external/llvm/docs/
DAdvancedBuilds.rst2 Advanced Build Configurations
11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
12 does not build the project, it generates the files needed by your build tool
25 The Clang CMake build system supports bootstrap (aka multi-stage) builds. At a
26 high level a multi-stage build is a chain of builds that pass data from one
28 bootstrap build.
30 In a simple two-stage bootstrap build, we build clang using the system compiler,
31 then use that just-built clang to build clang again. In CMake this simplest form
32 of a bootstrap build can be configured with a single option,
35 .. code-block:: console
[all …]
/external/libultrahdr/.github/workflows/
Dcmake.yml11 build:
15 - name: ubuntu-latest-gcc-cmake
16 os: ubuntu-latest
19 build-system: cmake
20 cmake-opts: '-DUHDR_BUILD_TESTS=1 -DUHDR_ENABLE_INSTALL=0 -DUHDR_BUILD_FUZZERS=0'
22 - name: ubuntu-latest-gcc-cmake-deps
23 os: ubuntu-latest
26 build-system: cmake
27 …cmake-opts: '-DUHDR_BUILD_TESTS=1 -DUHDR_ENABLE_INSTALL=0 -DUHDR_BUILD_FUZZERS=0 -DUHDR_BUILD_DEPS…
29 - name: ubuntu-latest-clang-cmake
[all …]
/external/sandboxed-api/.github/workflows/
Dubuntu-cmake.yml1 name: ubuntu-cmake
9 build:
11 fail-fast: false
14 # Ubuntu 22.04: Use preinstalled Clang 12.0.1, 13.0.1 and 14.0.0
15 - os: ubuntu-22.04
16 compiler: clang
17 compiler-version: 14
18 libclang-version: 14
19 pip-clang-version: "14.0"
20 ignore-errors: false
[all …]
/external/OpenCL-Headers/.github/workflows/
Dlinux.yml5 paths-ignore:
6 - '**/*.md'
8 paths-ignore:
9 - '**/*.md'
13 runs-on: ubuntu-20.04
14 container: streamhpc/opencl-sdk-base:ubuntu-18.04-20220127
25 - C_COMPILER: gcc-7
26 CXX_COMPILER: g++-7
31 - C_COMPILER: gcc-7
32 CXX_COMPILER: g++-7
[all …]
/external/flac/.github/workflows/
Daction.yml8 build:
12 - name: ubuntu-latest-clang-autotools
13 os: ubuntu-latest
14 cc: clang
15 cxx: clang++
16 build-system: autotools
17 configure-opts: ''
19 - name: ubuntu-latest-gcc-cmake
20 os: ubuntu-latest
23 build-system: cmake
[all …]
/external/clang/
DINSTALL.txt1 //===----------------------------------------------------------------------===//
2 // Clang Installation Instructions
3 //===----------------------------------------------------------------------===//
5 These instructions describe how to build and install Clang.
7 //===----------------------------------------------------------------------===//
9 //===----------------------------------------------------------------------===//
11 Clang is designed to be built as part of an LLVM build. Assuming that the LLVM
12 source code is located at $LLVM_SRC_ROOT, then the clang source code should be
15 $LLVM_SRC_ROOT/tools/clang
17 The directory is not required to be called clang, but doing so will allow the
[all …]
/external/bazelbuild-rules_go/go/
Dcrosstool.rst5 .. _Configuring CROSSTOOL: https://docs.bazel.build/versions/0.23.0/tutorial/crosstool.html
6 .. _Understanding CROSSTOOL: https://docs.bazel.build/versions/0.23.0/crosstool-reference.html
7 .. _Configuring C++ toolchains: https://docs.bazel.build/versions/master/tutorial/cc-toolchain-conf…
8 .. _cc_library: https://docs.bazel.build/versions/master/be/c-cpp.html#cc_library
12 .. _toolchain: https://docs.bazel.build/versions/master/be/platform.html#toolchain
16 ----------
23 ------------
27 TODOs. In particular, building and configuring a cross-compiling C++ toolchain
36 Bazel uses a CROSSTOOL file to configure the C/C++ toolchain, plus a few build
41 doesn't work with cross-compilation. Explicit configuration is required in these
[all …]
/external/trusty/arm-trusted-firmware/docs/getting_started/
Dinitial-build.rst1 Performing an Initial Build
4 - Before building TF-A, the environment variable ``CROSS_COMPILE`` must point
11 export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
17 export CROSS_COMPILE=<path-to-aarch32-gcc>/bin/arm-none-eabi-
19 It is possible to build TF-A using Clang or Arm Compiler 6. To do so
20 ``CC`` needs to point to the clang or armclang binary, which will
21 also select the clang or armclang assembler. Arm Compiler 6 will be selected
23 'armclang'. GNU binutils are required since the TF-A build system doesn't
32 export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
33 make CC=<path-to-armclang>/bin/armclang PLAT=<platform> all
[all …]
/external/clang/www/
Dget_started.html1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
5 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
6 <title>Clang - Getting Started</title>
12 <!--#include virtual="menu.html.incl"-->
16 <h1>Getting Started: Building and Running Clang</h1>
18 <p>This page gives you the shortest path to checking out Clang and demos a few
21 involved</a> with the Clang community. If you run into problems, please file
24 <h2 id="download">Release Clang Versions</h2>
26 <p>Clang is released as part of regular LLVM releases. You can download the release versions from <…
27 <p>Clang is also provided in all major BSD or GNU/Linux distributions as part of their respective p…
[all …]
/external/skia/site/docs/user/
Dbuild.md1 ---
2 title: 'How to build Skia'
3 linkTitle: 'How to build Skia'
6 ---
14 ## `is_official_build` and Third-party Dependencies
19 This mode configures Skia in a way that's suitable to ship: an optimized build
20 with no debug symbols, dynamically linked against its third-party dependencies
23 In contrast, the developer-oriented default is an unoptimized build with full
24 debug symbols and all third-party dependencies built from source and embedded
27 Skia offers several features that make use of third-party libraries, like
[all …]
/external/libkmsxx/
D.travis.yml5 # Only build test master & travis
8 - master
9 - travis
17 - libdrm-dev
18 - libegl1-mesa-dev
19 - libgles2-mesa-dev
20 - libwayland-dev
21 - libx11-xcb-dev
22 - libx11-dev
23 - libgbm-dev
[all …]
/external/arm-trusted-firmware/docs/getting_started/
Dinitial-build.rst1 Performing an Initial Build
4 - Before building TF-A, the environment variable ``CROSS_COMPILE`` must point
11 export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
17 export CROSS_COMPILE=<path-to-aarch32-gcc>/bin/arm-none-eabi-
19 It is possible to build TF-A using Clang or Arm Compiler 6. To do so
20 ``CC`` needs to point to the clang or armclang binary, which will
21 also select the clang or armclang assembler. Be aware that for Arm Compiler,
22 the GNU linker is used by default. However for Clang LLVM linker (LLD)
25 known to work with TF-A.
36 export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
[all …]

12345678910>>...47