| /third_party/skia/third_party/externals/freetype/docs/ |
| D | INSTALL.CROSS | 1 This document contains instructions on how to cross-build the FreeType
4 file `INSTALL.UNIX' for required tools and the basic self-building
9 -----------------
11 For self-building the FreeType library on a Unix system, GNU Make
15 The GNU C compiler to cross-build the target system is required.
16 Currently, using a non-GNU cross compiler is untested. The cross
17 compiler is expected to be installed with a system prefix. For
18 example, if your building system is FreeBSD/i386 and the target
19 system is Linux/MIPS, the cross compiler should be installed with
20 the name `mips-ip22-linuxelf-gcc'.
[all …]
|
| D | INSTALL.GNU | 1 This document contains instructions how to build the FreeType library
2 on non-Unix systems with the help of GNU Make. Note that if you are
7 FreeType 2 includes a powerful and flexible build system that allows
12 -------------------
14 The FreeType 2 build system relies on many features special to GNU
18 INSTALL A RECENT VERSION OF GNU MAKE ON YOUR SYSTEM!
26 pass option `--norc-substitution'.
31 make -v
39 ----------------
48 FreeType build system -- automatic system detection
[all …]
|
| /third_party/libsnd/.github/workflows/ |
| D | action.yml | 6 build:
8 fail-fast: false
11 ubuntu-gcc-autotools,
12 ubuntu-clang-autotools,
13 ubuntu-gcc-ossfuzz,
14 macos-autotools,
15 ubuntu-gcc-cmake,
16 ubuntu-gcc-cmake-shared,
17 ubuntu-clang-cmake,
18 ubuntu-clang-cmake-shared,
[all …]
|
| /third_party/rust/crates/cxx/book/src/ |
| D | building.md | 1 {{#title Multi-language build system options — Rust ♡ C++}}
2 # Multi-language build system options
4 CXX is designed to be convenient to integrate into a variety of build systems.
6 If you are working in a project that does not already have a preferred build
7 system for its C++ code *or* which will be relying heavily on open source
9 experience with Cargo which is the build system commonly used by open source
10 Rust projects. Refer to the ***[Cargo](build/cargo.md)*** chapter about CXX's
13 Among build systems designed for first class multi-language support, Bazel is a
14 solid choice. Refer to the ***[Bazel](build/bazel.md)*** chapter.
17 ***[CMake](build/cmake.md)*** chapter.
[all …]
|
| /third_party/icu/docs/userguide/icu4c/ |
| D | build.md | 1 ---
6 ---
7 <!--
10 -->
16 {: .no_toc .text-delta }
21 ---
23 ## Recommended Build Options
25 …he type of installation, we recommend a small number of modifications and build options. Note that…
28 … you have more time to update your code) revert to the default "using" via `-DU_USING_ICU_NAMESPAC…
33 --- icu4c/source/common/unicode/uversion.h (revision 40704)
[all …]
|
| /third_party/libsnd/ |
| D | README.md | 11 Erik de Castro Lopo <erikd@mega-nerd.com> aka @erikd. The project was developed
29 There are currently two build systems: the traditional GNU autotool based one and
30 modern CMake based build system. Use of the CMake build system is documented
33 Setting up a build environment for libsndfile on Debian or Ubuntu is as simple as:
35 sudo apt install autoconf autogen automake build-essential libasound2-dev \
36 libflac-dev libogg-dev libtool libvorbis-dev libopus-dev libmp3lame-dev \
37 libmpg123-dev pkg-config python
44 brew install autoconf autogen automake flac libogg libtool libvorbis opus mpg123 pkg-config
46 Once the build environment has been set up, building and testing libsndfile is
49 autoreconf -vif
[all …]
|
| /third_party/mesa3d/docs/ |
| D | meson.rst | 5 ---------------
10 **Mesa's Meson build system is generally considered stable and ready for
15 Mesa requires Meson >= 0.53.0 to build.
19 <https://mesonbuild.com/Getting-meson.html>`__ to install the
22 The Meson build of Mesa is tested on Linux, macOS, Windows, Cygwin,
25 Unix-like OSes
28 If Meson is not already installed on your system, you can typically
31 .. code-block:: console
33 sudo apt-get install meson # Ubuntu
37 .. code-block:: console
[all …]
|
| D | android.rst | 5 into the Android OS using the Android.mk build system on older versions
6 of Android, or out-of-tree using the Meson build system and the
9 The Android.mk build system has proven to be hard to maintain, as one
10 needs a built Android tree to build against, and it has never been
11 tested in CI. The meson build system flow is frequently used by
15 ------------------------------
19 ``~/.local/share/meson/cross/android-aarch64`` file::
22 ar = 'NDKDIR/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android-ar'
23 c = ['ccache', 'NDKDIR/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android29-clang']
24 …built/linux-x86_64/bin/aarch64-linux-android29-clang++', '-fno-exceptions', '-fno-unwind-tables', …
[all …]
|
| /third_party/icu/docs/processes/release/tasks/ |
| D | release-build.md | 1 ---
3 title: Release Build
7 ---
9 <!--
12 -->
14 # Release Build
18 {: .no_toc .text-delta }
23 ---
29 supports JRE 7 or later Java runtime environment. To avoid the Java's system
31 compiled with Java system libraries from JRE 7.*</span>
[all …]
|
| /third_party/ltp/doc/ |
| D | Build-System.rest | 1 Short introduction into LTP build system
6 the new and improved Makefile system.
15 -----------
17 The problem with the old Makefile system is that it was very difficult to
20 (maintenance). Furthermore, proper option-based cross-compilation was
22 system, and the appropriate implicit / static rules hadn't been configured to
23 compile into multiple object directories for out-of-tree build support (ease of
32 ------
34 The system was designed such that including a single GNU Makefile compatible
36 build the system.
[all …]
|
| /third_party/zlib/win32/ |
| D | DLL_FAQ.txt | 6 of the common DLL build of zlib, named ZLIB1.DLL. If you have
14 - ZLIB1.DLL is the common build of zlib as a DLL.
29 test programs that must run with a valid build of ZLIB1.DLL.
33 and build settings. If you do build the DLL yourself, please
38 If, for any reason, you need to build an incompatible DLL,
45 - The old ZLIB.DLL, built from zlib-1.1.4 or earlier, required
47 a static build. The DLL settings were supposed to be enabled
50 build time, resulting in two major problems:
53 the DLL, not all people added it to the build options. In
61 that were unable to run with the official ZLIB.DLL build.
[all …]
|
| /third_party/icu/tools/currency/src/com/ibm/icu/dev/tool/currency/ |
| D | Main.java | 22 * The tool used for ISO 4217 alpha3-numeric3 code mapping data maintenance.
23 * This code is used for synchronizing ICU alpha3-numeric3 mapping data with
30 BUILD, enumConstant
38 System.exit(1); in main()
52 } else if (args[0].equalsIgnoreCase(Command.BUILD.name())) { in main()
54 cmd = Command.BUILD; in main()
60 System.exit(1); in main()
65 if (cmd == Command.BUILD) { in main()
68 … OutputStreamWriter osw = new OutputStreamWriter(new FileOutputStream(outfile), "UTF-8"); in main()
100 System.out.println("[OK] ICU data is synchronized with the reference data"); in main()
[all …]
|
| /third_party/openssl/ |
| D | INSTALL.md | 1 Build and Install
11 - [Prerequisites](#prerequisites)
12 - [Notational Conventions](#notational-conventions)
13 - [Quick Installation Guide](#quick-installation-guide)
14 - [Building OpenSSL](#building-openssl)
15 - [Installing OpenSSL](#installing-openssl)
16 - [Configuration Options](#configuration-options)
17 - [API Level](#api-level)
18 - [Cross Compile Prefix](#cross-compile-prefix)
19 - [Build Type](#build-type)
[all …]
|
| /third_party/pcre2/pcre2/ |
| D | NON-AUTOTOOLS-BUILD | 2 --------------------------------------
22 C, and so should compile successfully on any system that has a Standard C
26 configure/make (autotools) build system, as found in many Unix-like
31 environments, though it can also be run in Unix-like environments. See the
36 provided for those who build PCRE2 without using "configure" or CMake. If you
43 code unit width: 8, 16, or 32 bits. You can build any combination of them. The
46 ahead to the CMake section. Note that the settings concerned with 8-bit,
47 16-bit, and 32-bit code units relate to the type of data string that PCRE2
48 processes. They are NOT referring to the underlying operating system bit width.
49 You do not have to do anything special to compile in a 64-bit environment, for
[all …]
|
| /third_party/pcre2/pcre2/doc/html/ |
| D | NON-AUTOTOOLS-BUILD.txt | 2 --------------------------------------
22 C, and so should compile successfully on any system that has a Standard C
26 configure/make (autotools) build system, as found in many Unix-like
31 environments, though it can also be run in Unix-like environments. See the
36 provided for those who build PCRE2 without using "configure" or CMake. If you
43 code unit width: 8, 16, or 32 bits. You can build any combination of them. The
46 ahead to the CMake section. Note that the settings concerned with 8-bit,
47 16-bit, and 32-bit code units relate to the type of data string that PCRE2
48 processes. They are NOT referring to the underlying operating system bit width.
49 You do not have to do anything special to compile in a 64-bit environment, for
[all …]
|
| /third_party/libwebsockets/contrib/ |
| D | cross-arm-android-gnueabi.cmake | 5 # cd build/
6 # cmake .. -DCMAKE_TOOLCHAIN_FILE=../cross-arm-linux-gnueabihf.cmake
9 set(CROSS_PATH /opt/libwebsockets_android/android-toolchain-arm)
11 # Target operating system name.
14 # Target build dynamic libs.
18 set(CMAKE_C_COMPILER "${CROSS_PATH}/bin/arm-linux-androideabi-gcc")
19 set(CMAKE_CXX_COMPILER "${CROSS_PATH}/bin/arm-linux-androideabi-g++")
22 # Different build system distros set release optimization level to different
23 # things according to their local policy, eg, Fedora is -O2 and Ubuntu is -O3
24 # here. Actually the build system's local policy is completely unrelated to
[all …]
|
| D | cross-arm-linux-gnueabihf.cmake | 5 # cd build/
6 # cmake .. -DCMAKE_TOOLCHAIN_FILE=../cross-arm-linux-gnueabihf.cmake
9 set(CROSS_PATH /opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.02-01-20130221_linux)
11 # Target operating system name.
15 set(CMAKE_C_COMPILER "${CROSS_PATH}/bin/arm-linux-gnueabihf-gcc")
16 set(CMAKE_CXX_COMPILER "${CROSS_PATH}/bin/arm-linux-gnueabihf-g++")
19 # Different build system distros set release optimization level to different
20 # things according to their local policy, eg, Fedora is -O2 and Ubuntu is -O3
21 # here. Actually the build system's local policy is completely unrelated to
22 # our desire for cross-build release optimization policy for code built to run
[all …]
|
| D | cross-ming.cmake | 5 # cd build/
6 # cmake .. -DCMAKE_TOOLCHAIN_FILE=../cross-ming.cmake
11 # Target operating system name.
16 set(CMAKE_C_COMPILER "${CROSS_PATH}/x86_64-w64-mingw32-gcc")
17 #set(CMAKE_CXX_COMPILER "${CROSS_PATH}/x86_64-w64-mingw32-g++")
18 set(CMAKE_RC_COMPILER "${CROSS_PATH}/x86_64-w64-mingw32-windres")
19 set(CMAKE_C_FLAGS "-Wno-error")
22 # Different build system distros set release optimization level to different
23 # things according to their local policy, eg, Fedora is -O2 and Ubuntu is -O3
24 # here. Actually the build system's local policy is completely unrelated to
[all …]
|
| D | cross-aarch64-qnx.cmake | 5 # cd build/
6 # cmake .. -DCMAKE_TOOLCHAIN_FILE=../cross-aarch64-qnx.cmake
12 # Target operating system name.
18 set(CMAKE_C_COMPILER "${CROSS_PATH}/bin/ntoaarch64-gcc")
19 set(CMAKE_CXX_COMPILER "${CROSS_PATH}/bin/ntoaarch64-g++")
21 set(CMAKE_C_FLAGS "-Wno-error")
25 # Different build system distros set release optimization level to different
26 # things according to their local policy, eg, Fedora is -O2 and Ubuntu is -O3
27 # here. Actually the build system's local policy is completely unrelated to
28 # our desire for cross-build release optimization policy for code built to run
[all …]
|
| D | cross-w64.cmake | 5 # cd build/
6 # cmake .. -DCMAKE_TOOLCHAIN_FILE=../contrib/cross-w64.cmake
13 set(CROSS_ROOT ${CROSS_PATH}/x86_64-w64-mingw32/sys-root/)
15 # Target operating system name.
20 set(CMAKE_C_COMPILER "${CROSS_PATH}/bin/x86_64-w64-mingw32-gcc")
21 set(CMAKE_CXX_COMPILER "${CROSS_PATH}/bin/x86_64-w64-mingw32-g++")
22 set(CMAKE_RC_COMPILER "${CROSS_PATH}/bin/x86_64-w64-mingw32-windres")
23 set(CMAKE_C_FLAGS "-Wno-error")
26 # Different build system distros set release optimization level to different
27 # things according to their local policy, eg, Fedora is -O2 and Ubuntu is -O3
[all …]
|
| /third_party/astc-encoder/Docs/ |
| D | Building.md | 6 Builds must use CMake 3.15 or higher as the build system generator. The
7 examples on this page show how to use it to generate build systems for NMake
8 (Windows) and Make (Linux and macOS), but CMake supports other build system
15 ### Configuring the build
17 To use CMake you must first configure the build. Create a build directory in
19 to generate the build system.
22 # Create a build directory
23 mkdir build
24 cd build
26 # Configure your build of choice, for example:
[all …]
|
| /third_party/icu/docs/userguide/icu/ |
| D | howtouseicu.md | 1 ---
6 ---
7 <!--
10 -->
16 {: .no_toc .text-delta }
21 ---
30 build other code using ICU.
32 For C++, note that there are [Recommended Build
33 Options](icu4c/build#recommended-build-options)
34 (both for normal use and for ICU as system-level libraries) which are not
[all …]
|
| /third_party/jerryscript/targets/openwrt/ |
| D | readme.md | 1 # JerryScript for OpenWrt build guide
4 for OpenWrt. For target device the TP-Link WR1043ND v1.x router is
10 As the TP-Link WR1043ND is a mips based device and mips is a big-endian
11 architecture a JerryScipt snapshot which was built on an little-endian
12 system will not work correctly. Thus it is advised that the
14 DO NOT run snapshots generated on little-endian system(s) on
15 a big-endian system.
25 To build the JerryScript for OpenWrt a toolchain is required for
31 ### 0. Install OpenWrt build requirements
33 $ sudo apt-get install git-core build-essential libssl-dev libncurses5-dev unzip gawk zlib1g-dev su…
[all …]
|
| /third_party/vulkan-loader/ |
| D | BUILD.md | 1 # Build Instructions
7 - [Build Instructions](#build-instructions)
8 - [Table Of Contents](#table-of-contents)
9 - [Contributing to the Repository](#contributing-to-the-repository)
10 - [Repository Content](#repository-content)
11 - [Installed Files](#installed-files)
12 - [Build Requirements](#build-requirements)
13 - [Test Requirements](#test-requirements)
14 - [Repository Set-Up](#repository-set-up)
15 - [Display Drivers](#display-drivers)
[all …]
|
| /third_party/curl/tests/ |
| D | testcurl.pl | 22 # SPDX-License-Identifier: curl
34 # curl-autocompile@haxx.se to be dealt with automatically (make sure the
36 # otherwise). The most current build status (with a reasonable backlog) will
40 # testcurl.pl [options] [curl-daily-name] > output
44 # --configure=[options] Configure options
45 # --crosscompile This is a crosscompile
46 # --desc=[desc] Description of your test system
47 # --email=[email] Set email address to report as
48 # --extvercmd=[command] Command to use for displaying version with cross compiles.
49 # --mktarball=[command] Command to run after completed test
[all …]
|