Lines Matching full:build

18 There are two ways to build flang. The first method is to build it at the same
19 time that you build all of the projects on which it depends. This is called
20 building in tree. The second method is to first do an in tree build to create
22 build, only build the flang code itself. This is called building standalone.
24 create the base build and base install areas, you can create multiple
30 All of the examples below use GCC as the C/C++ compilers and ninja as the build
38 tests.  You can use several different C++ compilers for most of the build,
40 compiler built in the initial part of the build.
44 into a directory called llvm-project.  The build will also
45 create subdirectories under the root directory called build (holds most of
50 the build.
64 rm -rf build
65 mkdir build
71 cd build
101 To run the flang tests on this build, execute the command in the "build"
114 To build compiler-rt:
142 Note that these instructions specify flang as one of the projects to build in
143 the in tree build.  This is not strictly necessary for subsequent standalone
148 To do the standalone build, start by building flang in tree as described above.
149 This build can be used as the  base build for several subsequent standalone
151 contains the subdirectory `build` that was created previously, for example:
155 Start each standalone build the same way by cloning the source for
165 rm -rf build
166 mkdir build
167 cd build
178   -DLLVM_BUILD_MAIN_SRC_DIR=$ROOTDIR/build/lib/cmake/llvm \
179   -DLLVM_EXTERNAL_LIT=$ROOTDIR/build/bin/llvm-lit \
181   -DLLVM_DIR=$ROOTDIR/build/lib/cmake/llvm \
182   -DCLANG_DIR=$ROOTDIR/build/lib/cmake/clang \
183   -DMLIR_DIR=$ROOTDIR/build/lib/cmake/mlir \
189 To run the flang tests on this build, execute the command in the `flang/build`
202 ##### CUDA build
223 CUDA toolkit version installed on the build machine.  If there are multiple
249 The result of the build is a "fat" library with the host and device
255 One may build Flang runtime library along with building Flang itself
257 build config:
281 ##### OpenMP target offload build
300 The result of the build is a "device-only" library, i.e. the host
305 The same set of CMake variables works for Flang in-tree build.
307 ### Build options
309 One may provide optional CMake variables to customize the build. Available options:
311 * `-DFLANG_RUNTIME_F128_MATH_LIB=libquadmath`: enables build of
314   `quadmath.h` must be available to the build compiler.
336 in order to build flang.
352 To build flang with clang,
354 and the GCC library and tools that were used to build clang++.
372 ### Build Types
374 To create a debug build,
380 To create a release build,
395 cd ~/flang/build
405  --param flang_site_config=<path-to-flang-build>/test-lit/lit.site.cfg.py \
406  --param flang_config=<path-to-flang-build>/test-lit/lit.cfg.py \
414 Note: Unit-tests will be skipped for LLVM install for an standalone build as it does not include go…
424 4. Invoking tests from <standalone flang build>/unittests/<respective unit test folder>
447 create `<build-dir>/tools/flang/docs/Dialect/FIRLangRef.md` in flang build directory.
454 cd ~/llvm-project/build
462     <build-dir>/tools/flang/docs/doxygen/html # for flang docs
476 cd ~/llvm-project/build
484    $BROWSER <build-dir>/tools/flang/docs/html/