Lines Matching refs:that

12 projects that use LLVM header files, libraries, and tools.  In order to use
15 * Set ``make`` variables. There are several variables that a ``Makefile`` needs
31 There are two ways that you can set all of these variables:
36 ``Makefiles``, a configure script that can be used to configure the location
48 code so that it can benefit from the build system's features. Mainly, you want
56 library that you build, you will have one directory in **lib** that will
57 contain that library's source code.
65 This subdirectory should contain any header files that are global to your
66 project. By global, we mean that they are used by more than one library or
77 For each program that you build, you will have one directory in **tools**
78 that will contain that program's source code.
82 This subdirectory should contain tests that verify that your code works
94 benchmarks and programs that are known to compile with the Clang front
100 provided within that directory on your own.
128 This is a space separated list of subdirectories that should be built. They
133 This is a list of directories that can be built in parallel. These will be
138 This is a list of directories that can be built if they exist, but will not
147 This variable contains the base name of the library that will be built. For
153 By default, a library is a ``.o`` file that is linked directly into a
167 This variable contains the name of the program that will be built. For
173 This variable holds a space separated list of libraries that should be
174 linked into the program. These libraries must be libraries that come from
179 Note that this works only for statically linked libraries.
183 This variable holds a space separated list of libraries that should be
186 link with a driver that performs an IR transformation you might set
191 Note that this works only for statically linked libraries. LLVM is split
199 This variable holds a space separated list of components that the LLVM
217 Note that ``LIBS`` must occur in the Makefile after the inclusion of
226 respectively. It is typically used to add options that tell the compiler
229 It is highly suggested that you append to ``CFLAGS`` and ``CPPFLAGS`` as
231 useful options in them that you may not want to overwrite.