| /external/libopus/.github/workflows/ |
| D | cmake.yml | 1 name: CMake
7 name: Test build with CMake 3.1.0
8 runs-on: ubuntu-20.04
10 - uses: actions/checkout@v3
12 fetch-depth: 0
13 - name: Download models
15 - name: Install CMake 3.1
17 …curl -sL https://github.com/Kitware/CMake/releases/download/v3.1.0/cmake-3.1.0-Linux-x86_64.sh -o …
19 sudo ./cmakeinstall.sh --prefix=/usr/local --exclude-subdir
21 sudo apt-get install libidn11
[all …]
|
| /external/libopenapv/.github/workflows/ |
| D | release_packages.yml | 9 build-linux:
10 runs-on: ubuntu-latest
12 - name: Checkout code
15 - name: Set up CMake
16 uses: jwlawson/actions-setup-cmake@v2
18 - name: Build PC Linux version of openAPV, generate packages and md5 file
20 cmake -S ${{github.workspace}} -B ${{github.workspace}}/build -DCMAKE_BUILD_TYPE=Release
21 cmake --build ${{github.workspace}}/build
23 cpack -C Release
25 - name: 'Upload PC Linux artifacts'
[all …]
|
| D | build.yml | 10 build-linux:
11 runs-on: ubuntu-latest
13 - name: Checkout code
16 - name: Set up CMake
17 uses: jwlawson/actions-setup-cmake@v2
19 - name: Build PC (Linux)
21 cmake -S ${{github.workspace}} -B ${{github.workspace}}/build -DCMAKE_BUILD_TYPE=Release
22 cmake --build ${{github.workspace}}/build
24 - name: Tar files
25 run: tar -cvf build-pc.tar .
[all …]
|
| /external/flac/.github/workflows/ |
| D | action.yml | 12 - name: ubuntu-latest-clang-autotools
13 os: ubuntu-latest
16 build-system: autotools
17 configure-opts: ''
19 - name: ubuntu-latest-gcc-cmake
20 os: ubuntu-latest
23 build-system: cmake
24 configure-opts: ''
26 - name: ubuntu-latest-clang-cmake
27 os: ubuntu-latest
[all …]
|
| /external/libpcap/doc/ |
| D | README.windows.md | 1 Building libpcap on Windows with Visual Studio
4 Unlike the UN*Xes on which libpcap can capture network traffic, Windows
15 ---------------------
26 such as a requirement to support versions of Windows earlier than
27 Windows Vista, which is the earliest version supported by Npcap.
34 C:\npcap-sdk, and put the contents of the ZIP archive into that folder.
45 --------------------
50 Building libpcap on Windows requires Visual Studio 2015 or later. The
56 Windows with which those tools, and other tools, can be installed; it
61 It is a command-line tool; a GUI tool, Chocolatey GUI, is provided as a
[all …]
|
| /external/boringssl/src/ |
| D | BUILDING.md | 9 The standalone CMake build is primarily intended for developers. If embedding
10 BoringSSL into another project with a pre-existing build system, see
17 * [CMake](https://cmake.org/download/) 3.12 or later is required.
19 * Building with [Ninja](https://ninja-build.org/) instead of Make is
20 recommended, because it makes builds faster. On Windows, CMake's Visual
22 recent versions of CMake for assembly support.
24 * On Windows only, [NASM](https://www.nasm.us/) is required. If not found
25 by CMake, it may be configured explicitly by setting
28 * Compilers for C11 and C++17, or later, are required. On Windows, MSVC from
29 Visual Studio 2022 or later with Windows 10 SDK 2104 or later are
[all …]
|
| /external/cronet/tot/third_party/boringssl/src/ |
| D | BUILDING.md | 9 The standalone CMake build is primarily intended for developers. If embedding
10 BoringSSL into another project with a pre-existing build system, see
17 * [CMake](https://cmake.org/download/) 3.12 or later is required.
19 * Building with [Ninja](https://ninja-build.org/) instead of Make is
20 recommended, because it makes builds faster. On Windows, CMake's Visual
22 recent versions of CMake for assembly support.
24 * On Windows only, [NASM](https://www.nasm.us/) is required. If not found
25 by CMake, it may be configured explicitly by setting
28 * Compilers for C11 and C++14, or later, are required. On Windows, MSVC from
29 Visual Studio 2022 or later with Windows 10 SDK 2104 or later are
[all …]
|
| /external/cronet/stable/third_party/boringssl/src/ |
| D | BUILDING.md | 9 The standalone CMake build is primarily intended for developers. If embedding
10 BoringSSL into another project with a pre-existing build system, see
17 * [CMake](https://cmake.org/download/) 3.12 or later is required.
19 * Building with [Ninja](https://ninja-build.org/) instead of Make is
20 recommended, because it makes builds faster. On Windows, CMake's Visual
22 recent versions of CMake for assembly support.
24 * On Windows only, [NASM](https://www.nasm.us/) is required. If not found
25 by CMake, it may be configured explicitly by setting
28 * Compilers for C11 and C++14, or later, are required. On Windows, MSVC from
29 Visual Studio 2022 or later with Windows 10 SDK 2104 or later are
[all …]
|
| /external/vulkan-validation-layers/ |
| D | BUILD.md | 3 Instructions for building this repository on Linux, Windows, Android, and
8 1. [Contributing](#contributing-to-the-repository)
9 1. [Repository Content](#repository-content)
10 1. [Repository Set-Up](#repository-set-up)
11 1. [Windows Build](#building-on-windows)
12 1. [Linux Build](#building-on-linux)
13 1. [Android Build](#building-on-android)
14 1. [MacOS build](#building-on-macos)
33 - *install_dir*`/lib` : The Vulkan validation layer libraries
34 - *install_dir*`/share/vulkan/explicit_layer.d` : The Vulkan validation layer
[all …]
|
| /external/libwebsockets/READMEs/ |
| D | README.build-windows.md | 1 # Some notes for the windows jungle
3 This was how I compiled libwebsockets starting from a blank windows install
4 in March - April 2020. Doing this on a linux distro is way simpler and quicker
13 ### Required: Windows product key
16 the windows it came with, you can recover your 'windows tax' windows product key
22 To have shared clipboard, and for windows video driver to match your vm window
23 resolution, you must install spice guest tools inside the windows VM. It also
26 https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe
28 ### Blood-pressure reduction: Firefox
30 https://www.mozilla.org/en-US/exp/firefox/
[all …]
|
| /external/cronet/stable/third_party/apache-portable-runtime/src/ |
| D | README.cmake | 1 Experimental cmake-based build support for APR on Microsoft Windows
4 ------
6 This build support is currently intended only for Microsoft Windows.
7 Only Windows NT-based systems can be targeted. (The traditional
8 Windows build support for APR can target Windows 9x as well.)
14 compatible with the previous Windows build support.
24 how to utilize the various cmake features, such as different
27 Please refer to the cmake documentation for additional information
28 that applies to building any project with cmake.
31 -------------
[all …]
|
| /external/cronet/tot/third_party/apache-portable-runtime/src/ |
| D | README.cmake | 1 Experimental cmake-based build support for APR on Microsoft Windows
4 ------
6 This build support is currently intended only for Microsoft Windows.
7 Only Windows NT-based systems can be targeted. (The traditional
8 Windows build support for APR can target Windows 9x as well.)
14 compatible with the previous Windows build support.
24 how to utilize the various cmake features, such as different
27 Please refer to the cmake documentation for additional information
28 that applies to building any project with cmake.
31 -------------
[all …]
|
| /external/tcpdump/doc/ |
| D | README.windows.md | 1 Building tcpdump on Windows with Visual Studio
4 Unlike the UN*Xes on which libpcap can capture network traffic, Windows
15 ---------------------
26 such as a requirement to support versions of Windows earlier than
27 Windows Vista, which is the earliest version supported by Npcap.
31 `C:\npcap-sdk`, and put the contents of the ZIP archive into that folder.
39 --------------------
44 Building tcpdump on Windows requires Visual Studio 2015 or later. The
49 Windows with which those tools, and other tools, can be installed; it
52 It is a command-line tool; a GUI tool, Chocolatey GUI, is provided as a
[all …]
|
| /external/capstone/ |
| D | COMPILE_CMAKE.TXT | 1 This documentation explains how to compile Capstone with CMake, focus on
6 To compile Capstone on Windows using Visual Studio, see COMPILE_MSVC.TXT.
8 *-*-*-*-*-*
10 This documentation requires CMake & Windows SDK or MS Visual Studio installed on
13 Get CMake for free from http://www.cmake.org.
20 run "cmake" with the unwanted archs disabled (set to 0) as followings.
22 - CAPSTONE_ARM_SUPPORT: support ARM. Run cmake with -DCAPSTONE_ARM_SUPPORT=0 to remove ARM.
23 …- CAPSTONE_ARM64_SUPPORT: support ARM64. Run cmake with -DCAPSTONE_ARM64_SUPPORT=0 to remove ARM64.
24 …- CAPSTONE_M680X_SUPPORT: support M680X. Run cmake with -DCAPSTONE_M680X_SUPPORT=0 to remove M680X.
25 - CAPSTONE_M68K_SUPPORT: support M68K. Run cmake with -DCAPSTONE_M68K_SUPPORT=0 to remove M68K.
[all …]
|
| /external/expat/expat/ |
| D | Changes | 14 !! - <blink>fixing a complex non-public security issue</blink>, !!
15 !! - teaming up on researching and fixing future security reports and !!
16 !! ClusterFuzz findings with few-days-max response times in communication !!
19 !! - implementing and auto-testing XML 1.0r5 support !!
21 !! - smart ideas on fixing the Autotools CMake files generation issue !!
23 !! - the Windows binaries topic (needs requirements engineering first), !!
24 !! - pushing migration from `int` to `size_t` further !!
25 !! including edge-cases test coverage (needs discussion before anything). !!
27 !! For details, please reach out via e-mail to sebastian@pipping.org so we !!
30 !! THANK YOU! Sebastian Pipping -- Berlin, 2024-03-09 !!
[all …]
|
| /external/grpc-grpc/ |
| D | BUILDING.md | 1 gRPC C++ - Building from source
5 …/cpp#to-start-using-grpc-c) instructions for guidance on how to add gRPC as a dependency to a C++ …
7 # Pre-requisites
12 $ [sudo] apt-get install build-essential autoconf libtool pkg-config
15 If you plan to build using CMake
17 $ [sudo] apt-get install cmake
23 $ [sudo] apt-get install clang libc++-dev
34 $ [sudo] xcode-select --install
44 If you plan to build using CMake, follow the instructions from https://cmake.org/download/
55 ## Windows section in Pre-requisites
[all …]
|
| /external/rust/android-crates-io/crates/grpcio-sys/grpc/ |
| D | BUILDING.md | 1 gRPC C++ - Building from source
5 …/cpp#to-start-using-grpc-c) instructions for guidance on how to add gRPC as a dependency to a C++ …
7 # Pre-requisites
12 $ [sudo] apt-get install build-essential autoconf libtool pkg-config
15 If you plan to build using CMake
17 $ [sudo] apt-get install cmake
23 $ [sudo] apt-get install clang libc++-dev
34 $ [sudo] xcode-select --install
44 If you plan to build using CMake, follow the instructions from https://cmake.org/download/
55 ## Windows section in Pre-requisites
[all …]
|
| /external/flatbuffers/.github/workflows/ |
| D | build.yml | 2 permissions: read-all
9 - "*" # new tag version, like `0.8.4` or else
11 - master
14 - master
17 - cron: '45 4 * * *'
20 build-linux:
24 digests-gcc: ${{ steps.hash-gcc.outputs.hashes }}
25 digests-clang: ${{ steps.hash-clang.outputs.hashes }}
27 runs-on: ubuntu-24.04
30 cxx: [g++-13, clang++-18]
[all …]
|
| /external/curl/docs/ |
| D | INSTALL-CMAKE.md | 1 <!--
4 SPDX-License-Identifier: curl
5 -->
7 # Building with CMake
10 from source code using the CMake build tool. To build with CMake, you of
11 course first have to install CMake. The minimum required version of CMake is
13 tree. Once the correct version of CMake is installed you can follow the
16 CMake builds can be configured either from the command line, or from one of
17 CMake's GUIs.
21 A CMake configuration of curl is similar to the autotools build of curl.
[all …]
|
| /external/pcre/doc/html/ |
| D | NON-AUTOTOOLS-BUILD.txt | 2 --------------------------------------
8 Stack size in Windows environments
9 Linking programs in Windows environments
10 Calling conventions in Windows environments
12 Building PCRE2 on Windows with CMake
13 Building PCRE2 on Windows with Visual Studio
26 configure/make (autotools) build system, as found in many Unix-like
30 There is also support for CMake, which some users prefer, especially in Windows
31 environments, though it can also be run in Unix-like environments. See the
32 section entitled "Building PCRE2 on Windows with CMake" below.
[all …]
|
| /external/pcre/ |
| D | NON-AUTOTOOLS-BUILD | 2 --------------------------------------
8 Stack size in Windows environments
9 Linking programs in Windows environments
10 Calling conventions in Windows environments
12 Building PCRE2 on Windows with CMake
13 Building PCRE2 on Windows with Visual Studio
26 configure/make (autotools) build system, as found in many Unix-like
30 There is also support for CMake, which some users prefer, especially in Windows
31 environments, though it can also be run in Unix-like environments. See the
32 section entitled "Building PCRE2 on Windows with CMake" below.
[all …]
|
| /external/libogg/ |
| D | README.md | 3 [](https://travis-ci.org/xi…
15 (eg, the modules libvorbis, vorbis-tools for the Vorbis music codec,
21 - `src` The source for libogg, a BSD-license inplementation of the public domain Ogg bitstream form…
23 - `include` Library API headers
25 - `doc` Ogg specification and libogg API documents
27 - `win32` Win32 projects and build automation
33 pre-built utilities may be found there.
62 #### Building on Windows ####
66 #### Cross-compiling from Linux to Windows ####
68 It is also possible to cross compile from Linux to windows using the MinGW
[all …]
|
| /external/libultrahdr/.github/workflows/ |
| D | cmake_win.yml | 1 name: Build and Test CI - Windows
2 # Build and Test CI for windows-latest
9 runs-on: ${{ matrix.config.os }}
11 fail-fast: true
14 # <Windows-latest, Release Build, Cl compiler toolchain, Visual Studio 17 2022 generator>
15 - name: "windows latest cl rel visual studio 17 2022 with deps"
16 os: windows-latest
20 … cmake-opts: '-DUHDR_BUILD_TESTS=1 -DUHDR_ENABLE_LOGS=1 -DUHDR_BUILD_DEPS=1 -DUHDR_ENABLE_WERROR=1'
23 - name: Checkout the repository
26 - name: Setup cmake
[all …]
|
| /external/libwebm/ |
| D | README.libwebm | 3 To build libwebm you must first create project files. To do this run cmake
6 Makefile.unix can be used as a fallback on systems that cmake does not
10 CMake Basics
13 run cmake with the path to the libwebm repo:
15 $ cmake path/to/libwebm
17 On Windows the above command will produce Visual Studio project files for the
21 To control what types of projects are generated the -G parameter is added to
22 the cmake command line. This argument must be followed by the name of a
23 generator. Running cmake with the --help argument will list the available
28 $ cmake path/to/libwebm -G Xcode
[all …]
|
| /external/google-fruit/.github/workflows/ |
| D | test-on-windows.yml | 1 name: Test on Windows
5 - master
10 …e tests with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
15 - cron: '13 8 1 * *'
18 runs-on: ${{matrix.config.runs_on}}
20 fail-fast: false
23 …- {runs_on: windows-2022, msvc_version_year: 2022, msvc_version: 17, multi_config: true, python_pa…
24 …- {runs_on: windows-2022, msvc_version_year: 2022, msvc_version: 17, multi_config: true, python_pa…
25 …- {runs_on: windows-2022, msvc_version_year: 2022, msvc_version: 17, multi_config: false, python_p…
26 …- {runs_on: windows-2022, msvc_version_year: 2022, msvc_version: 17, multi_config: false, python_p…
[all …]
|