Searched +full:build +full:- +full:mingw (Results 1 – 25 of 535) sorted by relevance
12345678910>>...22
| /third_party/libuv/.github/workflows/ |
| D | CI-win.yml | 1 name: CI-win
6 - '**'
7 - '!docs/**'
8 - '!src/unix/**'
9 - '!.**'
10 - '.github/workflows/CI-win.yml'
13 - v[0-9].*
14 - master
17 build-windows:
18 runs-on: windows-${{ matrix.config.server }}
[all …]
|
| /third_party/ffmpeg/doc/ |
| D | platform.texi | 1 \input texinfo @c -*- texinfo -*-
2 @documentencoding UTF-8
13 @chapter Unix-like
21 $(gcc -print-prog-name=as) --version
25 hard-coded path to gas. In the worst case pass @code{--disable-asm}
31 build your own shared library, you may need to force PIC support (with
32 @code{--enable-pic} during FFmpeg configure) and add the following option
36 -Wl,-Bsymbolic
40 pass the correct linking flag (e.g. @code{-pie}) to @code{--extra-ldexeflags}.
44 BSD make will not build FFmpeg, you need to install and use GNU Make
[all …]
|
| /third_party/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 \
13 # zlib1g-dev liblzma-dev libgcrypt-dev \
14 # python-dev python3-dev \
20 - |
21 ln -s /tests/xmlconf
[all …]
|
| /third_party/pcre2/pcre2/doc/html/ |
| D | NON-AUTOTOOLS-BUILD.txt | 2 --------------------------------------
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
49 You do not have to do anything special to compile in a 64-bit environment, for
58 libraries you are going to build. You must set all that apply.
61 -DHAVE_CONFIG_H to your compiler so that src/config.h is included in the
[all …]
|
| /third_party/pcre2/pcre2/ |
| D | NON-AUTOTOOLS-BUILD | 2 --------------------------------------
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
49 You do not have to do anything special to compile in a 64-bit environment, for
58 libraries you are going to build. You must set all that apply.
61 -DHAVE_CONFIG_H to your compiler so that src/config.h is included in the
[all …]
|
| /third_party/glfw/ |
| D | .appveyor.yml | 2 - Visual Studio 2015
5 - ci
6 - master
7 - latest
8 - 3.3-stable
12 - GENERATOR: MinGW Makefiles
14 CFLAGS: -Werror
15 - GENERATOR: MinGW Makefiles
17 CFLAGS: -Werror
18 - GENERATOR: Visual Studio 12 2013
[all …]
|
| /third_party/rust/rust/src/bootstrap/mk/ |
| D | Makefile.in | 3 BOOTSTRAP_ARGS := -v
12 $(Q)$(BOOTSTRAP) build --stage 2 $(BOOTSTRAP_ARGS)
13 $(Q)$(BOOTSTRAP) doc --stage 2 $(BOOTSTRAP_ARGS)
16 $(Q)echo 'Welcome to the rustbuild build system!'
19 $(Q)echo in this directory. To get the full power of the build system
22 $(Q)echo To learn more run \`./x.py --help\`
27 rustc-stage1:
28 $(Q)$(BOOTSTRAP) build --stage 1 library/test $(BOOTSTRAP_ARGS)
29 rustc-stage2:
30 $(Q)$(BOOTSTRAP) build --stage 2 library/test $(BOOTSTRAP_ARGS)
[all …]
|
| /third_party/openssl/ |
| D | NOTES-WINDOWS.md | 4 - [Native builds using Visual C++](#native-builds-using-visual-c++)
5 - [Native builds using Embarcadero C++Builder](
6 #native-builds-using-embarcadero-c++-builder)
7 - [Native builds using MinGW](#native-builds-using-mingw)
8 - [Linking native applications](#linking-native-applications)
9 - [Hosted builds using Cygwin](#hosted-builds-using-cygwin)
11 There are various options to build and run OpenSSL on the Windows platforms.
14 To build a native OpenSSL you can either use:
20 MinGW cross compiler
21 run on the GNU-like development environment MSYS2
[all …]
|
| /third_party/libcoap/ |
| D | BUILDING | 1 For Windows builds - see the Windows Section
12 * Change to the directory that you want to install the libcoap sub-directory
19 * Change to the directory that you want to install the libcoap sub-directory
21 * Then clone the latest (develop) version of the code:-
24 * Optionally, change the branch from develop to the stable main branch:-
42 General Building with cmake for linux/windows/macos/android (not for RIOT, LwIP or Contiki-NG - see…
45 cmake -E remove_directory build
46 cmake -E make_directory build
47 cd build
48 cmake .. -DENABLE_TESTS=ON
[all …]
|
| /third_party/rust/rust/compiler/rustc_codegen_cranelift/.github/workflows/ |
| D | main.yml | 4 - push
5 - pull_request
9 runs-on: ubuntu-latest
10 timeout-minutes: 10
13 - uses: actions/checkout@v3
15 - name: Install rustfmt
19 - name: Rustfmt
21 cargo fmt --check
22 rustfmt --check build_system/main.rs
23 rustfmt --check example/*
[all …]
|
| /third_party/ncurses/ |
| D | README.MinGW | 1 -------------------------------------------------------------------------------
2 -- Copyright 2020 Thomas E. Dickey --
3 -- Copyright 2008-2011,2012 Free Software Foundation, Inc. --
4 -- --
5 -- Permission is hereby granted, free of charge, to any person obtaining a --
6 -- copy of this software and associated documentation files (the --
7 -- "Software"), to deal in the Software without restriction, including --
8 -- without limitation the rights to use, copy, modify, merge, publish, --
9 -- distribute, distribute with modifications, sublicense, and/or sell copies --
10 -- of the Software, and to permit persons to whom the Software is furnished --
[all …]
|
| /third_party/skia/m133/third_party/externals/expat/expat/ |
| D | CMake.README | 1 == How to build expat with cmake (experimental) ==
3 The cmake based buildsystem for expat works on Windows (cygwin, mingw, Visual
6 Assuming ~/expat-2.6.3 is the source directory of expat, add a subdirectory
7 build and change into that directory:
8 ~/expat-2.6.3$ mkdir build && cd build
9 ~/expat-2.6.3/build$
13 ~/expat-2.6.3/build$ cmake ..
14 -- The C compiler identification is GNU
15 -- The CXX compiler identification is GNU
17 -- Configuring done
[all …]
|
| /third_party/skia/third_party/externals/expat/expat/ |
| D | CMake.README | 1 == How to build expat with cmake (experimental) ==
3 The cmake based buildsystem for expat works on Windows (cygwin, mingw, Visual
6 Assuming ~/expat-2.4.1 is the source directory of expat, add a subdirectory
7 build and change into that directory:
8 ~/expat-2.4.1$ mkdir build && cd build
9 ~/expat-2.4.1/build$
13 ~/expat-2.4.1/build$ cmake ..
14 -- The C compiler identification is GNU
15 -- The CXX compiler identification is GNU
17 -- Configuring done
[all …]
|
| /third_party/glfw/docs/ |
| D | compile.md | 6 build applications that use GLFW, see @ref build_guide.
16 compile_deps and @ref compile_options sections for GLFW-specific information.
25 If you are on a Unix-like system such as Linux, FreeBSD or Cygwin or have
31 [CMake user guide][cmake-guide] that includes everything in this guide not
34 [cmake-guide]: https://cmake.org/cmake/help/latest/guide/user-interaction/
39 The C/C++ development environments in Visual Studio, Xcode and MinGW come with
40 all necessary dependencies for compiling GLFW, but on Unix-like systems like
46 By default, both the Wayland and X11 backends are enabled on Linux and other Unix-like
48 or @ref GLFW_BUILD_X11 CMake options in the next step when generating build files.
52 None of the development packages above are needed to build or run programs that use an
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/marl/kokoro/windows/ |
| D | presubmit.bat | 7 REM https://www.apache.org/licenses/LICENSE-2.0
22 SET BUILD_DIR=%ROOT_DIR%\build
27 git submodule update --init
38 -G "%BUILD_GENERATOR%" ^
39 -A "%BUILD_TARGET_ARCH%" ^
40 "-DMARL_BUILD_TESTS=1" ^
41 "-DMARL_BUILD_EXAMPLES=1" ^
42 "-DMARL_BUILD_BENCHMARKS=1" ^
43 "-DMARL_WARNINGS_AS_ERRORS=1" ^
44 "-DMARL_DEBUG_ENABLED=1"
[all …]
|
| /third_party/rust/rust/src/doc/rustc/src/platform-support/ |
| D | pc-windows-gnullvm.md | 1 # \*-pc-windows-gnullvm
5 Windows targets similar to `*-pc-windows-gnu` but using UCRT as the runtime and various LLVM tools/…
8 - `aarch64-pc-windows-gnullvm`
9 - `x86_64-pc-windows-gnullvm`
13 - [@mati865](https://github.com/mati865)
17 The easiest way to obtain these targets is cross-compilation but native build from `x86_64-pc-windo…
18 Std support is expected to be on pair with `*-pc-windows-gnu`.
20 Binaries for this target should be at least on pair with `*-pc-windows-gnu` in terms of requirement…
28 …-compilation I recommend using [llvm-mingw](https://github.com/mstorsjo/llvm-mingw) toolchain, one…
33 Rust does not yet ship pre-compiled artifacts for this target. To compile for
[all …]
|
| /third_party/benchmark/ |
| D | appveyor.yml | 1 version: '{build}'
6 - Debug
7 - Release
11 - compiler: msvc-15-seh
14 - compiler: msvc-15-seh
17 - compiler: msvc-14-seh
20 - compiler: msvc-14-seh
23 - compiler: gcc-5.3.0-posix
24 generator: "MinGW Makefiles"
25 cxx_path: 'C:\mingw-w64\i686-5.3.0-posix-dwarf-rt_v4-rev0\mingw32\bin'
[all …]
|
| /third_party/gptfdisk/ |
| D | README.Windows | 6 Most versions of Windows cannot boot from a GPT disk on BIOS-based
12 GPT fdisk on a BIOS-mode boot disk, or perhaps even on a data disk, you may
13 find recovery to be very difficult! Pre-installed Windows 8 and later
15 self-installed Windows 8 systems sometimes use BIOS mode. This caveat does
23 the software. I originally wrote GPT fdisk on Linux, and some Linux- and
24 Unix-centric language remains in the documentation.
27 -----------------
31 text-mode program file as well as the sgdisk program that's available
34 Beginning with version 0.8.10, I'm distributing both 32-bit and 64-bit
35 binaries, which include the strings "32" or "64" in their names. The 32-bit
[all …]
|
| /third_party/lz4/ |
| D | appveyor.yml | 1 version: 1.0.{build}
4 - COMPILER: "gcc"
6 - COMPILER: "visual"
9 - COMPILER: "visual"
12 - COMPILER: "visual"
15 - COMPILER: "clang"
17 - COMPILER: "gcc"
21 - ECHO Installing %COMPILER% %PLATFORM% %CONFIGURATION%
22 - MKDIR bin
23 - if [%COMPILER%]==[visual] (
[all …]
|
| /third_party/rust/rust/src/ci/docker/host-x86_64/mingw-check/ |
| D | Dockerfile | 4 RUN apt-get update && apt-get install -y --no-install-recommends \
7 ninja-build \
10 ca-certificates \
12 python3-pip \
13 python3-pkg-resources \
18 xz-utils \
19 libssl-dev \
20 pkg-config \
21 mingw-w64 \
22 && rm -rf /var/lib/apt/lists/*
[all …]
|
| /third_party/rust/rust/src/ci/github-actions/ |
| D | ci.yml | 11 # ./x.py run src/tools/expand-yaml-anchors
16 ---
26 # YAML anchors work by defining an anchor with `&anchor-name` and reusing its
27 # content in another place with `*anchor-name`. The special `<<` map key merges
30 # The expand-yaml-anchors tool will automatically remove this block from the
32 x--expand-yaml-anchors--remove:
34 - &shared-ci-variables
40 - &public-variables
41 SCCACHE_BUCKET: rust-lang-ci-sccache2
42 TOOLSTATE_REPO: https://github.com/rust-lang-nursery/rust-toolstate
[all …]
|
| /third_party/rust/rust/ |
| D | README_zh.md | 3 …tps://img.shields.io/badge/Rust_Community%20-Join_us-brightgreen?style=plastic&logo=rust)](https:/…
8 [Rust]: https://www.rust-lang.org/
18 ["安装"]: https://doc.rust-lang.org/book/ch01-01-installation.html
19 [本书]： https://doc.rust-lang.org/book/index.html
40 关于 `x.py` 的更多信息，可以通过使用 `--help`标记来运行它
43 [gettingstarted]: https://rustc-dev-guide.rust-lang.org/getting-started.html
44 [rustcguidebuild]: https://rustc-dev-guide.rust-lang.org/building/how-to-build-and-run.html#what-is…
55 * 如果在 Linux 上编译并以 Linux 为目标，则需要 `pkg-config`
58 要编译 Cargo，还需要 OpenSSL（在大多数 Unix 发行版上为 `libssl-dev` 或 `openssl-devel` ）。
64 …[LLVM 的文档](https://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-l…
[all …]
|
| D | README.md | 3 …tps://img.shields.io/badge/Rust_Community%20-Join_us-brightgreen?style=plastic&logo=rust)](https:/…
8 [Rust]: https://www.rust-lang.org/
18 ["Installation"]: https://doc.rust-lang.org/book/ch01-01-installation.html
19 [The Book]: https://doc.rust-lang.org/book/index.html
23 The Rust build system uses a Python script called `x.py` to build the compiler,
26 settings for the build. You can see a full list of options in
40 More information about `x.py` can be found by running it with the `--help` flag
43 [gettingstarted]: https://rustc-dev-guide.rust-lang.org/getting-started.html
44 [rustcguidebuild]: https://rustc-dev-guide.rust-lang.org/building/how-to-build-and-run.html#what-is…
52 * A C compiler (when building for the host, `cc` is enough; cross-compiling may
[all …]
|
| /third_party/rust/rust/src/bootstrap/builder/ |
| D | tests.rs | 6 fn configure(cmd: &str, host: &[&str], target: &[&str]) -> Config { in configure()
10 fn configure_with_args(cmd: &[String], host: &[&str], target: &[&str]) -> Config { in configure_with_args()
17 … // But make sure to check out the `doc` and `rust-analyzer` submodules, since some steps need them in configure_with_args()
19 let submodule_build = Build::new(Config { in configure_with_args()
25 submodule_build.update_submodule(Path::new("src/tools/rust-analyzer")); in configure_with_args()
32 .join("tmp-rustbuild-tests") in configure_with_args()
33 .join(&thread::current().name().unwrap_or("unknown").replace(":", "-")); in configure_with_args()
36 config.build = TargetSelection::from_user("A"); in configure_with_args()
42 fn first<A, B>(v: Vec<(A, B)>) -> Vec<A> { in first()
46 fn run_build(paths: &[PathBuf], config: Config) -> Cache { in run_build()
[all …]
|
| /third_party/skia/third_party/externals/libjpeg-turbo/ |
| D | BUILDING.md | 1 Building libjpeg-turbo
5 Build Requirements
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.
30 build and install NASM from a source RPM by downloading one of the SRPMs from
[all …]
|
12345678910>>...22