Lines Matching refs:compiler

15 - When calling CMake for the first time, all needed compiler options must be
16   specified on the command line.  After this initial call to CMake, the compiler
37 - Notice in the example how the compiler definitions are only specified for an
91 **CMAKE_C_COMPILER** = <C compiler name>
92   Specify the C compiler.
94 **CMAKE_CXX_COMPILER** = <C++ compiler name>
95   Specify the C++ compiler.
97 **CMAKE_Fortran_COMPILER** = <Fortran compiler name>
98   Specify the Fortran compiler. This option is only needed when
100   compiler is not needed during the build.
109   Treat warnings as errors and fail, if a compiler warning is triggered.
115   Compiler to use for testing. Defaults to the compiler that was also used for
119   Compiler to use for testing. Defaults to the compiler that was also used for
123   Compiler to use for testing. Defaults to the compiler that was also used for
145   The default value for this option is chosen based on probing the compiler for
146   architecture macros (e.g., is ``__x86_64__`` predefined by compiler?).
170   Create the Fortran modules (requires Fortran compiler).
233   Additional C++ compiler flags.
245   Additional Fortran compiler flags.
277   Location of a CUDA compiler capable of emitting LLVM bitcode. Currently only
278   the Clang compiler is supported. This is only used when building the CUDA LLVM
281   clang), or the Clang compiler that the build uses as C compiler
293   Host compiler to use with NVCC. This compiler is not going to be used to
294   produce any binary. Instead, this is used to overcome the input compiler
295   checks done by NVCC. E.g. if using a default host compiler that is not
296   compatible with NVCC, this option can be use to pass to NVCC a valid compiler
340 - Build the library (architecture determined by probing compiler) using the
348 - Have CMake find the C/C++ compiler and specify additional flags for the
349   preprocessor and C++ compiler.