Lines Matching +full:- +full:dbuild_shared_libs

25     Clang should work on non-Windows platforms, and maybe on Windows too.
31     arm-linux-gnueabihf-gcc compiler:
34 …naro.org/14.11/components/toolchain/binaries/arm-linux-gnueabihf/gcc-linaro-4.9-2014.11-x86_64_arm…
35 …442e19cb1422db87068830305d90075feb1a3b  gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf.tar.xz |…
36     tar xf gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf.tar.xz && \
37     sudo mv gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf /opt/
46     cmake -GNinja ..
60 Note that the default build flags in the top-level `CMakeLists.txt` are for
63 If you want to cross-compile then there is an example toolchain file for 32-bit
67     cmake -DCMAKE_TOOLCHAIN_FILE=../util/32-bit-toolchain.cmake -GNinja ..
69 If you want to build as a shared library, pass `-DBUILD_SHARED_LIBS=1`. On
74 In order to serve environments where code-size is important as well as those
84 directory. Clone https://github.com/taka-no-me/android-cmake into `util/`.  Then
87     cmake -DANDROID_NATIVE_API_LEVEL=android-9 \
88           -DANDROID_ABI=armeabi-v7a \
89           -DCMAKE_TOOLCHAIN_FILE=../util/android-cmake/android.toolchain.cmake \
90           -DANDROID_NATIVE_API_LEVEL=16 \
91           -GNinja ..
93 Once you've run that twice, Ninja should produce Android-compatible binaries.
94 You can replace `armeabi-v7a` in the above with `arm64-v8a` to build aarch64
119 any illegal-instruction signal. But some environments don't support that sort
133 run-time, BoringSSL will likely crash.
138 are built by Ninja and can be run from the top-level directory with `go run
142 Both sets of tests may also be run with `ninja -C build run_tests`, but CMake