Home
last modified time | relevance | path

Searched +full:cross +full:- +full:compile (Results 1 – 25 of 1059) sorted by relevance

12345678910>>...43

/external/capstone/
DCOMPILE.TXT1 This documentation explains how to compile, install & run Capstone on MacOSX,
2 Linux, *BSD & Solaris. We also show steps to cross-compile for Microsoft Windows.
4 To natively compile for Windows using Microsoft Visual Studio, see COMPILE_MSVC.TXT.
6 To compile using CMake, see COMPILE_CMAKE.TXT.
8 To compile using XCode on MacOSX, see xcode/README.md.
10 To compile for Windows CE (a.k.a, Windows Embedded Compact), see windowsce/COMPILE.md.
12 *-*-*-*-*-*
14 Capstone requires no prerequisite packages, so it is easy to compile & install.
21 selected archs, choose the ones you want to compile in by editing "config.mk"
30 - CAPSTONE_ARCHS: specify list of architectures to compiled in.
[all …]
/external/ltp/.github/workflows/
Dci-docker-build.yml1 # Copyright (c) 2021-2024 Petr Vorel <pvorel@suse.cz>
11 runs-on: ubuntu-latest
14 fail-fast: false
18 - container: "debian:stable"
23 # cross compilation builds
24 - container: "debian:stable"
27 CC: powerpc64le-linux-gnu-gcc
30 VARIANT: cross-compile
32 - container: "debian:stable"
35 CC: aarch64-linux-gnu-gcc
[all …]
/external/ComputeLibrary/docs/user_guide/
Dhow_to_build_and_run_examples.dox2 /// Copyright (c) 2017-2023 Arm Limited.
4 /// SPDX-License-Identifier: MIT
33 To see the build options available simply run ```scons -h```
41 - gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf
42 - gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu
44 To cross-compile the library in debug mode, with Arm® Neon™ only support, for Linux 32bit:
46 scons Werror=1 -j8 debug=1 neon=1 opencl=0 os=linux arch=armv7a
48 To cross-compile the library in asserts mode, with OpenCL only support, for Linux 64bit:
50 scons Werror=1 -j8 debug=0 asserts=1 neon=0 opencl=1 embed_kernels=1 os=linux arch=armv8a
52 You can also compile the library natively on an Arm device by using <b>build=native</b>:
[all …]
/external/clang/docs/
DCrossCompilation.rst2 Cross-compilation using Clang
9 for cross-compiling your code to a different architecture. It assumes you
10 already know how to compile the code in question for the host architecture,
17 `instructions for cross-compiling LLVM itself
21 related to cross-compilation, and what main compiler options Clang provides
22 for performing cross-compilation.
24 Cross compilation issues
33 On the other hand, Clang/LLVM is natively a cross-compiler, meaning that
34 one set of programs can compile to all targets by setting the ``-target``
35 option. That makes it a lot easier for programmers wishing to compile to
[all …]
/external/ltp/
Dbuild.sh2 # Copyright (c) 2017-2021 Petr Vorel <pvorel@suse.cz>
5 set -e
7 CFLAGS="${CFLAGS:--Wformat -Werror=format-security -Werror=implicit-function-declaration -Werror=re…
8 CC="${CC:-gcc}"
10 DEFAULT_PREFIX="$HOME/ltp-install"
14 CONFIGURE_OPTS_IN_TREE="--with-open-posix-testsuite --with-realtime-testsuite $CONFIGURE_OPT_EXTRA"
15 # TODO: open posix testsuite is currently broken in out-tree-build. Enable it once it's fixed.
16 CONFIGURE_OPTS_OUT_TREE="--with-realtime-testsuite $CONFIGURE_OPT_EXTRA"
19 BUILD_DIR="$SRC_DIR/../ltp-build"
21 MAKE_OPTS="-j$(getconf _NPROCESSORS_ONLN)"
[all …]
/external/bazelbuild-rules_rust/examples/bzlmod/cross_compile/
DREADME.md1 # Cross Compilation
3 For cross compilation, you have to specify a custom platform to let Bazel know that you are compili…
5 The example code is setup to cross compile from the following hosts to the the following targets:
7 * {linux, x86_64} -> {linux, aarch64}
8 * {darwin, x86_64} -> {linux, x86_64}
9 * {darwin, x86_64} -> {linux, aarch64}
10 * {darwin, aarch64 (Apple Silicon)} -> {linux, x86_64}
11 * {darwin, aarch64 (Apple Silicon)} -> {linux, aarch64}
13 You cross-compile by calling the target.
34 …DULE.bazel, second configure LLVM and Rust for cross compilation, and third the configuration of t…
[all …]
/external/rust/android-crates-io/crates/libusb1-sys/
DREADME.md3 The `libusb1-sys` crate provides declarations and linkage for the `libusb` C library. Following the
4 `*-sys` package conventions, the `libusb1-sys` crate does not define higher-level abstractions over
8 In order to use the `libusb1-sys` crate, you must have the `libusb` library installed where it can …
9 found by `pkg-config`.
11 All systems supported by `libusb` are also supported by the `libusb1-sys` crate. It's been tested on
14 ### Cross-Compiling
15 To link to a cross-compiled version of the native `libusb` library, it's necessary to set several
16 environment variables to configure `pkg-config` to work with a cross-compiler's sysroot. [Autotools
18 cross-compilation](https://autotools.io/pkgconfig/cross-compiling.html) with `pkg-config`.
20 However, Rust's [`pkg-config` build helper](https://github.com/alexcrichton/pkg-config-rs) doesn't
[all …]
/external/tensorflow/tensorflow/lite/tools/pip_package/
DREADME.md11 sudo apt install swig libjpeg-dev zlib1g-dev python3-dev python3-numpy
19 pip install --upgrade <wheel>
23 the following command will cross-compile tflite-runtime package for python2.7
27 make BASE_IMAGE=debian:buster PYTHON=python TENSORFLOW_TARGET=rpi docker-build
28 make BASE_IMAGE=debian:buster PYTHON=python3 TENSORFLOW_TARGET=rpi docker-build
31 Another option is to cross-compile for python3.5 (from Debian Stretch) on ARM64
35 make BASE_IMAGE=debian:stretch PYTHON=python3 TENSORFLOW_TARGET=aarch64 docker-build
42 make BASE_IMAGE=ubuntu:18.04 PYTHON=python3 TENSORFLOW_TARGET=native docker-build
49 make BASE_IMAGE=debian:buster PYTHON=python3 TENSORFLOW_TARGET=rpi BUILD_DEB=y docker-build
56 This approach can leverage TF's ci_build.sh for ARM cross builds.
[all …]
/external/angle/build/toolchain/
Dcros_toolchain.gni2 # Use of this source code is governed by a BSD-style license that can be
5 # CrOS builds must cross-compile on a Linux host for the actual CrOS
8 # control the cross-compilation tool chain. However, requiring such
9 # fine-grain specification is tedious for build-bots and developers.
17 # To perform a board-specific build, first obtain the correct system
19 # by setting appropriate cross-compilation variables.
21 # For example, to compile a Chrome source tree in /g/src for an
24 # cross-compilation with RBE acceleration. (NB: additional variables
25 # will be necessary to successfully compile a working CrOS Chrome. See
28 # target_sysroot= /g/.cros_cache/chrome-sdk/tarballs/auron_paine+7644.0.0+sysroot_chromeos-base_chr…
[all …]
/external/llvm/docs/
DHowToCrossCompileLLVM.rst2 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).
26 * ``ninja-build`` (from backports in Ubuntu)
27 * ``gcc-4.7-arm-linux-gnueabihf``
28 * ``gcc-4.7-multilib-arm-linux-gnueabihf``
29 * ``binutils-arm-linux-gnueabihf``
[all …]
/external/crosvm/third_party/libslirp-rs/
DREADME.md4 libslirp-rs project that has been tightly integrated with `net_util`.
6 libslirp-rs depends on a bunch of libraries (libslirp and its dependencies).
20 pacman -S mingw-w64-x86_64-meson ninja git mingw-w64-x86_64-gcc mingw-w64-x86_64-glib2 mingw-w64-x8…
31 ninja -C build
37 [libglib-2.0-0.dll](https://packages.msys2.org/package/mingw-w64-x86_64-glib2) and glib inturn
38 depends on a few other libraries. On linux libglib-2.0-0.dll is not available as a dll with mingw
40 get them prebuilt from somewhere. Once you have those, create a file name `cross-compile` in
44 c = 'x86_64-w64-mingw32-gcc'
45 cpp = 'x86_64-w64-mingw32-g++'
46 ar = 'x86_64-w64-mingw32-ar'
[all …]
/external/rust/android-crates-io/crates/grpcio-sys/grpc/third_party/cares/cares/
DINSTALL.md1 ** This file is adapted from libcurl and not yet fully rewritten for c-ares! **
9 How To Compile
15 Lots of people download binary distributions of c-ares. This document
16 does not describe how to install c-ares using such a binary package.
17 This document describes how to compile, build and install c-ares from
24 release tarball, see the [GIT-INFO](GIT-INFO) file in the root directory
47 [GIT-INFO](GIT_INFO) on how to proceed.
51 ./configure --help
53 If you want to install c-ares in a different file hierarchy than /usr/local,
56 ./configure --prefix=/path/to/c-ares/tree
[all …]
/external/libogg/
DREADME.md3 [![Travis Build Status](https://travis-ci.org/xiph/ogg.svg?branch=master)](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.
64 Use the project file in the win32 directory. It should compile out of the box.
66 #### Cross-compiling from Linux to Windows ####
68 It is also possible to cross compile from Linux to windows using the MinGW
[all …]
/external/flashrom/doc/dev_guide/
Dbuilding_from_source.rst9 * pkg-config
10 * sphinx-build*
12 | \* optional, to build man-pages and html documentation
17 * linux-headers [#b2]_
22 * NI-845x driver & library package [#b3]_
28 If you are cross compiling, install the dependencies for your target.
31 -----
35 meson compile -C builddir
36 meson test -C builddir
37 meson install -C builddir
[all …]
/external/libwebsockets/READMEs/
DREADME.build.md8 ./bootstrap-vcpkg.sh
16 CMake is a multi-platform build tool that can generate build files for many
19 CMake also allows/recommends you to do "out of source"-builds, that is,
27 - Windows (Visual Studio)
28 - Windows (MinGW)
29 - Linux (x86 and ARM)
30 - OSX
31 - NetBSD
42 see below on how to toggle compile options.
71 as --prefix= with autotools. It defaults to /usr/local.
[all …]
/external/speex/
DREADME.blackfin6 1/ In order to cross-compile for uClinux from the SpeexDSP tarball:
8 ./configure --enable-blackfin-asm --enable-fixed-point --host=bfin-uclinux
12 The --enable-blackfin-asm option is not required, but it speeds up Speex by
15 2/ In order to cross-compile for uClinux from the SpeexDSP git:
20 ./configure --enable-blackfin-asm --enable-fixed-point --host=bfin-uclinux
/external/toybox/mkroot/
DREADME1 mkroot - simple linux system builder
3 Compiles a toybox-based root filesystem and kernel that can boot under qemu.
6 launched via ./run-qemu.sh (which assumes you have QEMU installed, KVM
12 --- Quick Start
15 and one or more musl cross compiler toolchain(s) in the "ccc" directory:
19 $ wget https://landley.net/bin/toolchains/latest/i686-linux-musl-cross.tar.xz
21 $ tar xvJCf ccc i686-linux-musl-cross.tar.xz
25 $ mkroot/mkroot.sh CROSS=i686 LINUX=linux
26 $ root/i686/run-qemu.sh
31 --- Building without a cross compiler (warning: glibc sucks)
[all …]
/external/cronet/tot/third_party/lss/tests/
DREADME.md38 Simply run `make`. This will compile & execute all the tests on your local
44 We have rudimentary cross-compile testing via gcc and clang. Try running
45 `make cross` -- for any toolchains you don't have available, it should skip
49 The cross-compilers can be created using <http://crosstool-ng.github.io/>.
/external/cronet/stable/third_party/lss/tests/
DREADME.md38 Simply run `make`. This will compile & execute all the tests on your local
44 We have rudimentary cross-compile testing via gcc and clang. Try running
45 `make cross` -- for any toolchains you don't have available, it should skip
49 The cross-compilers can be created using <http://crosstool-ng.github.io/>.
/external/sdv/vsomeip/third_party/boost/numeric/odeint/performance/SIMD/
DMakefile13 INCLUDES = -I$(BOOST_ROOT) -I${SIMD_INCLUDE}
16 # change this if you want to cross-compile
23 CXXFLAGS = -O3 -x${ARCH} -std=c++0x -fno-alias -inline-forceinline -DNDEBUG ${INCLUDES}
24 # -ip
27 # change this if you want to cross-compile
29 # # ARCH = core-avx-i
33 # CXXFLAGS = -O3 -ffast-math -mtune=${ARCH} -march=${ARCH} -std=c++0x -DNDEBUG ${INCLUDES}
/external/libdav1d/
DREADME.md5 **dav1d** is an **AV1** cross-platform **d**ecoder, open-source, and focused on speed and correctne…
7 It is now battle-tested and production-ready and can be used everywhere.
17 It supports all features from AV1, including all subsampling and bit-depth parameters.
23 …her VideoLAN projects, so that it can be embedded anywhere, including non-open-source software; or…
25 …is the same as for libvorbis, see [RMS on vorbis](https://lwn.net/2001/0301/a/rms-ov-license.php3).
38 7. Make high bit-depth fast on mobile, by writing asm for ARMv8 chips.
40 9. Make high bit-depth fast on older mobile, by writing asm for ARMv7 chips,
41 10. Make high bit-depth fast on desktop, by writing asm for AVX2 chips,
42 11. Make high bit-depth fast on older desktop, by writing asm for SSSE3+ chips,
45 ### On-going
[all …]
/external/cronet/tot/third_party/google_benchmark/src/cmake/
DCXXFeatureCheck.cmake1 # - Compile and run code to check for C++ features
9 # - Example
28 add_definitions(-DHAVE_${VAR})
40 message(STATUS "Cross-compiling to test ${FEATURE}")
50 "If you see build failures due to cross compilation, try setting HAVE_${VAR} to 0")
68 message(STATUS "Performing Test ${FEATURE} -- success")
70 add_definitions(-DHAVE_${VAR})
74 message(STATUS "Performing Test ${FEATURE} -- failed to compile: ${COMPILE_OUTPUT_VAR}")
76 message(STATUS "Performing Test ${FEATURE} -- failed to compile")
79 message(STATUS "Performing Test ${FEATURE} -- compiled but failed to run")
/external/google-benchmark/cmake/
DCXXFeatureCheck.cmake1 # - Compile and run code to check for C++ features
9 # - Example
28 add_definitions(-DHAVE_${VAR})
40 message(STATUS "Cross-compiling to test ${FEATURE}")
50 "If you see build failures due to cross compilation, try setting HAVE_${VAR} to 0")
68 message(STATUS "Performing Test ${FEATURE} -- success")
70 add_definitions(-DHAVE_${VAR})
74 message(STATUS "Performing Test ${FEATURE} -- failed to compile: ${COMPILE_OUTPUT_VAR}")
76 message(STATUS "Performing Test ${FEATURE} -- failed to compile")
79 message(STATUS "Performing Test ${FEATURE} -- compiled but failed to run")
/external/cronet/stable/third_party/google_benchmark/src/cmake/
DCXXFeatureCheck.cmake1 # - Compile and run code to check for C++ features
9 # - Example
28 add_definitions(-DHAVE_${VAR})
40 message(STATUS "Cross-compiling to test ${FEATURE}")
50 "If you see build failures due to cross compilation, try setting HAVE_${VAR} to 0")
68 message(STATUS "Performing Test ${FEATURE} -- success")
70 add_definitions(-DHAVE_${VAR})
74 message(STATUS "Performing Test ${FEATURE} -- failed to compile: ${COMPILE_OUTPUT_VAR}")
76 message(STATUS "Performing Test ${FEATURE} -- failed to compile")
79 message(STATUS "Performing Test ${FEATURE} -- compiled but failed to run")
/external/cronet/tot/third_party/icu/source/
Dacinclude.m43 # Copyright (c) 1999-2016, International Business Machines Corporation and
18 *-*-solaris*)
20 icu_cv_host_frag=mh-solaris-gcc
22 icu_cv_host_frag=mh-solaris
24 alpha*-*-linux-gnu)
26 icu_cv_host_frag=mh-alpha-linux-gcc
28 icu_cv_host_frag=mh-alpha-linux-cc
30 powerpc*-*-linux*)
32 icu_cv_host_frag=mh-linux
34 icu_cv_host_frag=mh-linux-va
[all …]

12345678910>>...43