Lines Matching full:build

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:
37 A single CMake configure can build multiple binaries for a single target CPU
39 will include the build variant as a postfix. It is possible to build any set of
48 Once you have configured the build you can use NMake to compile the project
49 from your build dir, and install to your target install directory.
52 # Run a build and install build outputs in `${CMAKE_INSTALL_PREFIX}/bin/`
53 cd build
64 ### Configuring the build
66 To use CMake you must first configure the build. Create a build directory
68 to generate the build system.
74 # Create a build directory
75 mkdir build
76 cd build
78 # Configure your build of choice, for example:
88 # macOS universal binary build
92 A single CMake configure can build multiple binaries for a single target CPU
94 will include the build variant as a postfix. It is possible to build any set of
97 For macOS, we additionally support the ability to build a universal binary.
98 This build includes SSE4.1 (`x86_64`), AVX2 (`x86_64h`), and NEON (`arm64`)
99 build slices in a single output binary. The OS will select the correct variant
100 to run for the machine being used. This is the default build target for a macOS
101 build, but single-target binaries can still be built by setting
107 Once you have configured the build you can use Make to compile the project from
108 your build dir, and install to your target install directory.
111 # Run a build and install build outputs in `${CMAKE_INSTALL_PREFIX}/bin/`
113 cd build
122 ### Configuring the build
124 To use CMake you must first configure the build. Create a build directory
126 to generate the build system.
129 # Create a build directory
130 mkdir build
131 cd build
133 # Configure a universal build
139 Once you have configured the build you can use CMake to compile the project
140 from your build dir, and install to your target install directory.
143 cmake --build . --config Release
149 ## Advanced build options
152 the build system.
154 ### Build Types
160 | Release          | Optimized release build                                  |
161 | RelWithDebInfo   | Optimized release build with debug info                  |
162 | Debug            | Unoptimized debug build with debug info                  |
170 option `-DASTCENC_SHAREDLIB=ON` at configure time. For macOS build targets the
171 shared library supports the same universal build configuration as the command
175 are an extra build output that are not currently used by the command line tool.
181 performance can be improved by limiting the block sizes supported in the build
183 when configuring. Legal block sizes that are unavailable in a restricted build
188 All normal builds are designed to be invariant, so any build from the same git
199 development purposes it is possible to build an intrinsic-free build which uses
217 To build unit tests add `-DASTCENC_UNITTEST=ON` to the CMake command line when
220 To run unit tests use the CMake `ctest` utility from your build directory after
224 cd build
231 supports it. To build binaries with ASAN checking enabled add `-DASTCENC_ASAN=ON`
237 development build for testing on e.g. different Arm CPU microarchitectures.
239 The build script below shows one possible route to building the command line tool for Android. Once
249 BUILD_DIR=build
257     -DCMAKE_TOOLCHAIN_FILE=${ANDROID_NDK}/build/cmake/android.toolchain.cmake \
274 the current CMake configuration using the `package` build target
282 # Run a build and package build outputs in `./astcenc-<ver>-<os>-<arch>.<fmt>`
283 cd build