Lines Matching +full:ninja +full:- +full:test +full:- +full:arm64

6 BoringSSL into another project with a pre-existing build system, see
24   * Building with [Ninja](https://ninja-build.org/) instead of Make is
35     Recent versions of GCC (4.8+) and Clang should work on non-Windows
43     [libunwind](https://www.nongnu.org/libunwind/) dependency to test the
48 Using Ninja (note the 'N' is capitalized in the cmake invocation):
52     cmake -GNinja ..
53     ninja
66 Note that the default build flags in the top-level `CMakeLists.txt` are for
67 debugging—optimisation isn't enabled. Pass `-DCMAKE_BUILD_TYPE=Release` to
70 If you want to cross-compile then there is an example toolchain file for 32-bit
74     cmake -DCMAKE_TOOLCHAIN_FILE=../util/32-bit-toolchain.cmake -GNinja ..
76 If you want to build as a shared library, pass `-DBUILD_SHARED_LIBS=1`. On
81 In order to serve environments where code-size is important as well as those
85 See [CMake's documentation](https://cmake.org/cmake/help/v3.4/manual/cmake-variables.7.html)
97     cmake -DANDROID_ABI=armeabi-v7a \
98           -DCMAKE_TOOLCHAIN_FILE=${ANDROID_NDK}/build/cmake/android.toolchain.cmake \
99           -DANDROID_NATIVE_API_LEVEL=16 \
100           -GNinja ..
102 Once you've run that, Ninja should produce Android-compatible binaries.  You
103 can replace `armeabi-v7a` in the above with `arm64-v8a` and use API level 21 or
110 `arm` or `arm64`.
112     adb push ${ANDROID_NDK}/prebuilt/android-ARCH/gdbserver/gdbserver \
118 architecture of the host machine, e.g. `linux-x86_64`.
125 To build for iOS, pass `-DCMAKE_OSX_SYSROOT=iphoneos` and
126 `-DCMAKE_OSX_ARCHITECTURES=ARCH` to CMake, where `ARCH` is the desired
127 architecture, matching values used in the `-arch` flag in Apple's toolchain.
129 Passing multiple architectures for a multiple-architecture build is not
143 -DBORINGSSL_PREFIX=MY_CUSTOM_PREFIX
144 -DBORINGSSL_PREFIX_SYMBOLS=/path/to/symbols.txt` will configure the build to add
170 By default, on Linux-based systems, BoringSSL will try to use `getauxval` and
178 `-march` flag. You can also define any of the following to enable the
188 run-time, BoringSSL will likely crash.
192 The implementations of some algorithms require a trade-off between binary size
193 and performance. For instance, BoringSSL's fastest P-256 implementation uses a
194 148 KiB pre-computed table. To optimize instead for binary size, pass
195 `-DOPENSSL_SMALL=1` to CMake or define the `OPENSSL_SMALL` preprocessor symbol.
200 are built by Ninja and can be run from the top-level directory with `go run
201 util/all_tests.go`. The latter have to be run separately by running `go test`
202 from within `ssl/test/runner`.
204 Both sets of tests may also be run with `ninja -C build run_tests`, but CMake
205 3.2 or later is required to avoid Ninja's output buffering.