/3rd_party/llvm/docs/Projects.html

https://code.google.com/p/softart/ · HTML · 489 lines · 390 code · 81 blank · 18 comment · 0 complexity · a64f09b7756116ddf30a9b7ad94e758e MD5 · raw file 

    

  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"

    2. 

  2.                       "http://www.w3.org/TR/html4/strict.dtd">

    3. 

  3. <html>

    4. 

  4. <head>

    5. 

  5.   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

    6. 

  6.   <title>Creating an LLVM Project</title>

    7. 

  7.   <link rel="stylesheet" href="llvm.css" type="text/css">

    8. 

  8. </head>

    9. 

  9. <body>

    10. 

  10. 

    11. 

  11. <h1>Creating an LLVM Project</h1>

    12. 

  12. 

    13. 

  13. <ol>

    14. 

  14. <li><a href="#overview">Overview</a></li>

    15. 

  15. <li><a href="#create">Create a project from the Sample Project</a></li>

    16. 

  16. <li><a href="#source">Source tree layout</a></li>

    17. 

  17. <li><a href="#makefiles">Writing LLVM-style Makefiles</a>

    18. 

  18.   <ol>

    19. 

  19.   <li><a href="#reqVars">Required Variables</a></li>

    20. 

  20.   <li><a href="#varsBuildDir">Variables for Building Subdirectories</a></li>

    21. 

  21.   <li><a href="#varsBuildLib">Variables for Building Libraries</a></li>

    22. 

  22.   <li><a href="#varsBuildProg">Variables for Building Programs</a></li>

    23. 

  23.   <li><a href="#miscVars">Miscellaneous Variables</a></li>

    24. 

  24.   </ol></li>

    25. 

  25. <li><a href="#objcode">Placement of object code</a></li>

    26. 

  26. <li><a href="#help">Further help</a></li>

    27. 

  27. </ol>

    28. 

  28. 

    29. 

  29. <div class="doc_author">

    30. 

  30.   <p>Written by John Criswell</p>

    31. 

  31. </div>

    32. 

  32. 

    33. 

  33. <!-- *********************************************************************** -->

    34. 

  34. <h2><a name="overview">Overview</a></h2>

    35. 

  35. <!-- *********************************************************************** -->

    36. 

  36. 

    37. 

  37. <div>

    38. 

  38. 

    39. 

  39. <p>The LLVM build system is designed to facilitate the building of third party

    40. 

  40. projects that use LLVM header files, libraries, and tools.  In order to use

    41. 

  41. these facilities, a Makefile from a project must do the following things:</p>

    42. 

  42. 

    43. 

  43. <ol>

    44. 

  44.   <li>Set <tt>make</tt> variables. There are several variables that a Makefile

    45. 

  45.   needs to set to use the LLVM build system:

    46. 

  46.   <ul>

    47. 

  47.     <li><tt>PROJECT_NAME</tt> - The name by which your project is known.</li>

    48. 

  48.     <li><tt>LLVM_SRC_ROOT</tt> - The root of the LLVM source tree.</li>

    49. 

  49.     <li><tt>LLVM_OBJ_ROOT</tt> - The root of the LLVM object tree.</li>

    50. 

  50.     <li><tt>PROJ_SRC_ROOT</tt> - The root of the project's source tree.</li>

    51. 

  51.     <li><tt>PROJ_OBJ_ROOT</tt> - The root of the project's object tree.</li>

    52. 

  52.     <li><tt>PROJ_INSTALL_ROOT</tt> - The root installation directory.</li>

    53. 

  53.     <li><tt>LEVEL</tt> - The relative path from the current directory to the

    54. 

  54.     project's root ($PROJ_OBJ_ROOT).</li>

    55. 

  55.   </ul></li>

    56. 

  56.   <li>Include <tt>Makefile.config</tt> from <tt>$(LLVM_OBJ_ROOT)</tt>.</li>

    57. 

  57.   <li>Include <tt>Makefile.rules</tt> from <tt>$(LLVM_SRC_ROOT)</tt>.</li>

    58. 

  58. </ol>

    59. 

  59. 

    60. 

  60. <p>There are two ways that you can set all of these variables:</p>

    61. 

  61. <ol>

    62. 

  62.   <li>You can write your own Makefiles which hard-code these values.</li>

    63. 

  63.   <li>You can use the pre-made LLVM sample project. This sample project

    64. 

  64.   includes Makefiles, a configure script that can be used to configure the

    65. 

  65.   location of LLVM, and the ability to support multiple object directories

    66. 

  66.   from a single source directory.</li>

    67. 

  67. </ol>

    68. 

  68. 

    69. 

  69. <p>This document assumes that you will base your project on the LLVM sample

    70. 

  70. project found in <tt>llvm/projects/sample</tt>.  If you want to devise your own

    71. 

  71. build system, studying the sample project and LLVM Makefiles will probably

    72. 

  72. provide enough information on how to write your own Makefiles.</p>

    73. 

  73. 

    74. 

  74. </div>

    75. 

  75. 

    76. 

  76. <!-- *********************************************************************** -->

    77. 

  77. <h2>

    78. 

  78.   <a name="create">Create a Project from the Sample Project</a>

    79. 

  79. </h2>

    80. 

  80. <!-- *********************************************************************** -->

    81. 

  81. 

    82. 

  82. <div>

    83. 

  83. 

    84. 

  84. <p>Follow these simple steps to start your project:</p>

    85. 

  85. 

    86. 

  86. <ol>

    87. 

  87. <li>Copy the <tt>llvm/projects/sample</tt> directory to any place of your

    88. 

  88. choosing.  You can place it anywhere you like.  Rename the directory to match

    89. 

  89. the name of your project.</li>

    90. 

  90. 

    91. 

  91. <li>

    92. 

  92. If you downloaded LLVM using Subversion, remove all the directories named .svn

    93. 

  93. (and all the files therein) from your project's new source tree.  This will

    94. 

  94. keep Subversion from thinking that your project is inside

    95. 

  95. <tt>llvm/trunk/projects/sample</tt>.</li>

    96. 

  96. 

    97. 

  97. <li>Add your source code and Makefiles to your source tree.</li>

    98. 

  98. 

    99. 

  99. <li>If you want your project to be configured with the <tt>configure</tt> script

    100. 

  100. then you need to edit <tt>autoconf/configure.ac</tt> as follows:

    101. 

  101.   <ul>

    102. 

  102.     <li><b>AC_INIT</b>. Place the name of your project, its version number and

    103. 

  103.     a contact email address for your project as the arguments to this macro</li>

    104. 

  104.     <li><b>AC_CONFIG_AUX_DIR</b>. If your project isn't in the

    105. 

  105.     <tt>llvm/projects</tt> directory then you might need to adjust this so that

    106. 

  106.     it specifies a relative path to the <tt>llvm/autoconf</tt> directory.</li>

    107. 

  107.     <li><b>LLVM_CONFIG_PROJECT</b>. Just leave this alone.</li>

    108. 

  108.     <li><b>AC_CONFIG_SRCDIR</b>. Specify a path to a file name that identifies

    109. 

  109.     your project; or just leave it at <tt>Makefile.common.in</tt></li>

    110. 

  110.     <li><b>AC_CONFIG_FILES</b>. Do not change.</li>

    111. 

  111.     <li><b>AC_CONFIG_MAKEFILE</b>. Use one of these macros for each Makefile

    112. 

  112.     that your project uses. This macro arranges for your makefiles to be copied

    113. 

  113.     from the source directory, unmodified, to the build directory.</li>

    114. 

  114.   </ul>

    115. 

  115. </li>

    116. 

  116. 

    117. 

  117. <li>After updating <tt>autoconf/configure.ac</tt>, regenerate the

    118. 

  118. configure script with these commands:

    119. 

  119. 

    120. 

  120. <div class="doc_code">

    121. 

  121. <p><tt>% cd autoconf<br>

    122. 

  122.        % ./AutoRegen.sh</tt></p>

    123. 

  123. </div>

    124. 

  124. 

    125. 

  125. <p>You must be using Autoconf version 2.59 or later and your aclocal version

    126. 

  126. should be 1.9 or later.</p></li>

    127. 

  127. 

    128. 

  128. <li>Run <tt>configure</tt> in the directory in which you want to place

    129. 

  129. object code.  Use the following options to tell your project where it

    130. 

  130. can find LLVM:

    131. 

  131. 

    132. 

  132.   <dl>

    133. 

  133.     <dt><tt>--with-llvmsrc=&lt;directory&gt;</tt></dt>

    134. 

  134.     <dd>Tell your project where the LLVM source tree is located.</dd>

    135. 

  135.     <dt><br><tt>--with-llvmobj=&lt;directory&gt;</tt></dt>

    136. 

  136.     <dd>Tell your project where the LLVM object tree is located.</dd>

    137. 

  137.     <dt><br><tt>--prefix=&lt;directory&gt;</tt></dt>

    138. 

  138.     <dd>Tell your project where it should get installed.</dd>

    139. 

  139.   </dl>

    140. 

  140. </ol>

    141. 

  141. 

    142. 

  142. <p>That's it!  Now all you have to do is type <tt>gmake</tt> (or <tt>make</tt>

    143. 

  143. if your on a GNU/Linux system) in the root of your object directory, and your

    144. 

  144. project should build.</p>

    145. 

  145. 

    146. 

  146. </div>

    147. 

  147. 

    148. 

  148. <!-- *********************************************************************** -->

    149. 

  149. <h2>

    150. 

  150.   <a name="source">Source Tree Layout</a>

    151. 

  151. </h2>

    152. 

  152. <!-- *********************************************************************** -->

    153. 

  153. 

    154. 

  154. <div>

    155. 

  155. 

    156. 

  156. <p>In order to use the LLVM build system, you will want to organize your

    157. 

  157. source code so that it can benefit from the build system's features.

    158. 

  158. Mainly, you want your source tree layout to look similar to the LLVM

    159. 

  159. source tree layout.  The best way to do this is to just copy the

    160. 

  160. project tree from <tt>llvm/projects/sample</tt> and modify it to meet

    161. 

  161. your needs, but you can certainly add to it if you want.</p>

    162. 

  162. 

    163. 

  163. <p>Underneath your top level directory, you should have the following

    164. 

  164. directories:</p>

    165. 

  165. 

    166. 

  166. <dl>

    167. 

  167.   <dt><b>lib</b>

    168. 

  168.   <dd>

    169. 

  169.   This subdirectory should contain all of your library source

    170. 

  170.   code.  For each library that you build, you will have one

    171. 

  171.   directory in <b>lib</b> that will contain that library's source

    172. 

  172.   code.

    173. 

  173. 

    174. 

  174.   <p>

    175. 

  175.   Libraries can be object files, archives, or dynamic libraries.

    176. 

  176.   The <b>lib</b> directory is just a convenient place for libraries

    177. 

  177.   as it places them all in a directory from which they can be linked

    178. 

  178.   later.

    179. 

  179. 

    180. 

  180.   <dt><b>include</b>

    181. 

  181.   <dd>

    182. 

  182.   This subdirectory should contain any header files that are

    183. 

  183.   global to your project.  By global, we mean that they are used

    184. 

  184.   by more than one library or executable of your project.

    185. 

  185.   <p>

    186. 

  186.   By placing your header files in <b>include</b>, they will be

    187. 

  187.   found automatically by the LLVM build system.  For example, if

    188. 

  188.   you have a file <b>include/jazz/note.h</b>, then your source

    189. 

  189.   files can include it simply with <b>#include "jazz/note.h"</b>.

    190. 

  190. 

    191. 

  191.   <dt><b>tools</b>

    192. 

  192.   <dd>

    193. 

  193.   This subdirectory should contain all of your source

    194. 

  194.   code for executables.  For each program that you build, you

    195. 

  195.   will have one directory in <b>tools</b> that will contain that

    196. 

  196.   program's source code.

    197. 

  197.   <p>

    198. 

  198. 

    199. 

  199.   <dt><b>test</b>

    200. 

  200.   <dd>

    201. 

  201.   This subdirectory should contain tests that verify that your code

    202. 

  202.   works correctly.  Automated tests are especially useful.

    203. 

  203.   <p>

    204. 

  204.   Currently, the LLVM build system provides basic support for tests.

    205. 

  205.   The LLVM system provides the following:

    206. 

  206.   <ul>

    207. 

  207.     <li>

    208. 

  208.     LLVM provides a tcl procedure that is used by Dejagnu to run

    209. 

  209.     tests.  It can be found in <tt>llvm/lib/llvm-dg.exp</tt>.  This

    210. 

  210.     test procedure uses RUN lines in the actual test case to determine

    211. 

  211.     how to run the test.  See the <a

    212. 

  212.     href="TestingGuide.html">TestingGuide</a> for more details. You

    213. 

  213.     can easily write Makefile support similar to the Makefiles in

    214. 

  214.     <tt>llvm/test</tt> to use Dejagnu to run your project's tests.<br></li>

    215. 

  215.     <li>

    216. 

  216.     LLVM contains an optional package called <tt>llvm-test</tt>

    217. 

  217.     which provides benchmarks and programs that are known to compile with the

    218. 

  218.     LLVM GCC front ends.  You can use these

    219. 

  219.     programs to test your code, gather statistics information, and

    220. 

  220.     compare it to the current LLVM performance statistics.

    221. 

  221.     <br>Currently, there is no way to hook your tests directly into the

    222. 

  222.     <tt>llvm/test</tt> testing harness.  You will simply

    223. 

  223.     need to find a way to use the source provided within that directory

    224. 

  224.     on your own.

    225. 

  225.   </ul>

    226. 

  226. </dl>

    227. 

  227. 

    228. 

  228. <p>Typically, you will want to build your <b>lib</b> directory first followed by

    229. 

  229. your <b>tools</b> directory.</p>

    230. 

  230. 

    231. 

  231. </div>

    232. 

  232. 

    233. 

  233. <!-- *********************************************************************** -->

    234. 

  234. <h2>

    235. 

  235.   <a name="makefiles">Writing LLVM Style Makefiles</a>

    236. 

  236. </h2>

    237. 

  237. <!-- *********************************************************************** -->

    238. 

  238. 

    239. 

  239. <div>

    240. 

  240. 

    241. 

  241. <p>The LLVM build system provides a convenient way to build libraries and

    242. 

  242. executables.  Most of your project Makefiles will only need to define a few

    243. 

  243. variables.  Below is a list of the variables one can set and what they can

    244. 

  244. do:</p>

    245. 

  245. 

    246. 

  246. <!-- ======================================================================= -->

    247. 

  247. <h3>

    248. 

  248.   <a name="reqVars">Required Variables</a>

    249. 

  249. </h3>

    250. 

  250. 

    251. 

  251. <div>

    252. 

  252. 

    253. 

  253. <dl>

    254. 

  254.   <dt>LEVEL

    255. 

  255.   <dd>

    256. 

  256.   This variable is the relative path from this Makefile to the

    257. 

  257.   top directory of your project's source code.  For example, if

    258. 

  258.   your source code is in <tt>/tmp/src</tt>, then the Makefile in

    259. 

  259.   <tt>/tmp/src/jump/high</tt> would set <tt>LEVEL</tt> to <tt>"../.."</tt>.

    260. 

  260. </dl>

    261. 

  261. 

    262. 

  262. </div>

    263. 

  263. 

    264. 

  264. <!-- ======================================================================= -->

    265. 

  265. <h3>

    266. 

  266.   <a name="varsBuildDir">Variables for Building Subdirectories</a>

    267. 

  267. </h3>

    268. 

  268. 

    269. 

  269. <div>

    270. 

  270. 

    271. 

  271. <dl>

    272. 

  272.   <dt>DIRS

    273. 

  273.   <dd>

    274. 

  274.   This is a space separated list of subdirectories that should be

    275. 

  275.   built.  They will be built, one at a time, in the order

    276. 

  276.   specified.

    277. 

  277.   <p>

    278. 

  278. 

    279. 

  279.   <dt>PARALLEL_DIRS

    280. 

  280.   <dd>

    281. 

  281.   This is a list of directories that can be built in parallel.

    282. 

  282.   These will be built after the directories in DIRS have been

    283. 

  283.   built.

    284. 

  284.   <p>

    285. 

  285. 

    286. 

  286.   <dt>OPTIONAL_DIRS

    287. 

  287.   <dd>

    288. 

  288.   This is a list of directories that can be built if they exist,

    289. 

  289.   but will not cause an error if they do not exist.  They are

    290. 

  290.   built serially in the order in which they are listed.

    291. 

  291. </dl>

    292. 

  292. 

    293. 

  293. </div>

    294. 

  294. 

    295. 

  295. <!-- ======================================================================= -->

    296. 

  296. <h3>

    297. 

  297.   <a name="varsBuildLib">Variables for Building Libraries</a>

    298. 

  298. </h3>

    299. 

  299. 

    300. 

  300. <div>

    301. 

  301. 

    302. 

  302. <dl>

    303. 

  303.   <dt>LIBRARYNAME

    304. 

  304.   <dd>

    305. 

  305.   This variable contains the base name of the library that will

    306. 

  306.   be built.  For example, to build a library named

    307. 

  307.   <tt>libsample.a</tt>, LIBRARYNAME should be set to

    308. 

  308.   <tt>sample</tt>.

    309. 

  309.   <p>

    310. 

  310. 

    311. 

  311.   <dt>BUILD_ARCHIVE

    312. 

  312.   <dd>

    313. 

  313.   By default, a library is a <tt>.o</tt> file that is linked

    314. 

  314.   directly into a program.  To build an archive (also known as

    315. 

  315.   a static library), set the BUILD_ARCHIVE variable.

    316. 

  316.   <p>

    317. 

  317. 

    318. 

  318.   <dt>SHARED_LIBRARY

    319. 

  319.   <dd>

    320. 

  320.   If SHARED_LIBRARY is defined in your Makefile, a shared

    321. 

  321.   (or dynamic) library will be built.

    322. 

  322. </dl>

    323. 

  323. 

    324. 

  324. </div>

    325. 

  325. 

    326. 

  326. <!-- ======================================================================= -->

    327. 

  327. <h3>

    328. 

  328.   <a name="varsBuildProg">Variables for Building Programs</a>

    329. 

  329. </h3>

    330. 

  330. 

    331. 

  331. <div>

    332. 

  332. 

    333. 

  333. <dl>

    334. 

  334.   <dt>TOOLNAME

    335. 

  335.   <dd>

    336. 

  336.   This variable contains the name of the program that will

    337. 

  337.   be built.  For example, to build an executable named

    338. 

  338.   <tt>sample</tt>, TOOLNAME should be set to <tt>sample</tt>.

    339. 

  339.   <p>

    340. 

  340. 

    341. 

  341.   <dt>USEDLIBS

    342. 

  342.   <dd>

    343. 

  343.   This variable holds a space separated list of libraries that should

    344. 

  344.   be linked into the program.  These libraries must be libraries that

    345. 

  345.   come from your <b>lib</b> directory.  The libraries must be

    346. 

  346.   specified without their "lib" prefix.  For example, to link

    347. 

  347.   libsample.a, you would set USEDLIBS to

    348. 

  348.   <tt>sample.a</tt>.

    349. 

  349.   <p>

    350. 

  350.   Note that this works only for statically linked libraries.

    351. 

  351.   <p>

    352. 

  352. 

    353. 

  353.   <dt>LLVMLIBS

    354. 

  354.   <dd>

    355. 

  355.   This variable holds a space separated list of libraries that should

    356. 

  356.   be linked into the program.  These libraries must be LLVM libraries.

    357. 

  357.   The libraries must be specified without their "lib" prefix.  For

    358. 

  358.   example, to link with a driver that performs an IR transformation

    359. 

  359.   you might set LLVMLIBS to this minimal set of libraries

    360. 

  360.   <tt>LLVMSupport.a LLVMCore.a LLVMBitReader.a LLVMAsmParser.a LLVMAnalysis.a LLVMTransformUtils.a LLVMScalarOpts.a LLVMTarget.a</tt>.

    361. 

  361.   <p>

    362. 

  362.   Note that this works only for statically linked libraries. LLVM is

    363. 

  363.   split into a large number of static libraries, and the list of libraries you

    364. 

  364.   require may be much longer than the list above. To see a full list

    365. 

  365.   of libraries use:

    366. 

  366.   <tt>llvm-config --libs all</tt>.

    367. 

  367.   Using LINK_COMPONENTS as described below, obviates the need to set LLVMLIBS.

    368. 

  368.   <p>

    369. 

  369. 

    370. 

  370.   <dt>LINK_COMPONENTS

    371. 

  371.   <dd>This variable holds a space separated list of components that

    372. 

  372.   the LLVM Makefiles pass to the <tt>llvm-config</tt> tool to generate

    373. 

  373.   a link line for the program. For example, to link with all LLVM

    374. 

  374.   libraries use

    375. 

  375.   <tt>LINK_COMPONENTS = all</tt>.

    376. 

  376.   <p>

    377. 

  377. 

    378. 

  378.   <dt>LIBS

    379. 

  379.   <dd>

    380. 

  380.   To link dynamic libraries, add <tt>-l&lt;library base name&gt;</tt> to

    381. 

  381.   the LIBS variable.  The LLVM build system will look in the same places

    382. 

  382.   for dynamic libraries as it does for static libraries.

    383. 

  383.   <p>

    384. 

  384.   For example, to link <tt>libsample.so</tt>, you would have the

    385. 

  385.   following line in your <tt>Makefile</tt>:

    386. 

  386.   <p>

    387. 

  387.   <tt>

    388. 

  388.   LIBS += -lsample

    389. 

  389.   </tt>

    390. 

  390.   <p>

    391. 

  391.   Note that LIBS must occur in the Makefile after the inclusion of Makefile.common.

    392. 

  392.   <p>

    393. 

  393. </dl>

    394. 

  394. 

    395. 

  395. </div>

    396. 

  396. 

    397. 

  397. <!-- ======================================================================= -->

    398. 

  398. <h3>

    399. 

  399.   <a name="miscVars">Miscellaneous Variables</a>

    400. 

  400. </h3>

    401. 

  401. 

    402. 

  402. <div>

    403. 

  403. 

    404. 

  404. <dl>

    405. 

  405.   <dt>ExtraSource

    406. 

  406.   <dd>

    407. 

  407.   This variable contains a space separated list of extra source

    408. 

  408.   files that need to be built.  It is useful for including the

    409. 

  409.   output of Lex and Yacc programs.

    410. 

  410.   <p>

    411. 

  411. 

    412. 

  412.   <dt>CFLAGS

    413. 

  413.   <dt>CPPFLAGS

    414. 

  414.   <dd>

    415. 

  415.   This variable can be used to add options to the C and C++

    416. 

  416.   compiler, respectively.  It is typically used to add options

    417. 

  417.   that tell the compiler the location of additional directories

    418. 

  418.   to search for header files.

    419. 

  419.   <p>

    420. 

  420.   It is highly suggested that you append to CFLAGS and CPPFLAGS as

    421. 

  421.   opposed to overwriting them.  The master Makefiles may already

    422. 

  422.   have useful options in them that you may not want to overwrite.

    423. 

  423.   <p>

    424. 

  424. </dl>

    425. 

  425. 

    426. 

  426. </div>

    427. 

  427. 

    428. 

  428. </div>

    429. 

  429. 

    430. 

  430. <!-- *********************************************************************** -->

    431. 

  431. <h2>

    432. 

  432.   <a name="objcode">Placement of Object Code</a>

    433. 

  433. </h2>

    434. 

  434. <!-- *********************************************************************** -->

    435. 

  435. 

    436. 

  436. <div>

    437. 

  437. 

    438. 

  438. <p>The final location of built libraries and executables will depend upon

    439. 

  439. whether you do a Debug, Release, or Profile build.</p>

    440. 

  440. 

    441. 

  441. <dl>

    442. 

  442.   <dt>Libraries

    443. 

  443.   <dd>

    444. 

  444.   All libraries (static and dynamic) will be stored in

    445. 

  445.   <tt>PROJ_OBJ_ROOT/&lt;type&gt;/lib</tt>, where type is <tt>Debug</tt>,

    446. 

  446.   <tt>Release</tt>, or <tt>Profile</tt> for a debug, optimized, or

    447. 

  447.   profiled build, respectively.<p>

    448. 

  448. 

    449. 

  449.   <dt>Executables

    450. 

  450.   <dd>All executables will be stored in

    451. 

  451.   <tt>PROJ_OBJ_ROOT/&lt;type&gt;/bin</tt>, where type is <tt>Debug</tt>,

    452. 

  452.   <tt>Release</tt>, or <tt>Profile</tt> for a debug, optimized, or profiled

    453. 

  453.   build, respectively.

    454. 

  454. </dl>

    455. 

  455. 

    456. 

  456. </div>

    457. 

  457. 

    458. 

  458. <!-- *********************************************************************** -->

    459. 

  459. <h2>

    460. 

  460.   <a name="help">Further Help</a>

    461. 

  461. </h2>

    462. 

  462. <!-- *********************************************************************** -->

    463. 

  463. 

    464. 

  464. <div>

    465. 

  465. 

    466. 

  466. <p>If you have any questions or need any help creating an LLVM project,

    467. 

  467. the LLVM team would be more than happy to help.  You can always post your

    468. 

  468. questions to the <a

    469. 

  469. href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM Developers

    470. 

  470. Mailing List</a>.</p>

    471. 

  471. 

    472. 

  472. </div>

    473. 

  473. 

    474. 

  474. <!-- *********************************************************************** -->

    475. 

  475. <hr>

    476. 

  476. <address>

    477. 

  477.   <a href="http://jigsaw.w3.org/css-validator/check/referer"><img

    478. 

  478.   src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>

    479. 

  479.   <a href="http://validator.w3.org/check/referer"><img

    480. 

  480.   src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>

    481. 

  481. 

    482. 

  482.   <a href="mailto:criswell@uiuc.edu">John Criswell</a><br>

    483. 

  483.   <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a>

    484. 

  484.   <br>

    485. 

  485.   Last modified: $Date: 2011-11-03 14:43:23 +0800 (Thu, 03 Nov 2011) $

    486. 

  486. </address>

    487. 

  487. 

    488. 

  488. </body>

    489. 

  489. </html>
    490.