the name of your project.</li>
<li>
-If you downloaded LLVM using CVS, remove all the directories named CVS (and all
-the files therein) from your project's new source tree. This will keep CVS
-from thinking that your project is inside <tt>llvm/projects/sample</tt>.
-</li>
+If you downloaded LLVM using Subversion, remove all the directories named .svn
+(and all the files therein) from your project's new source tree. This will
+keep Subversion from thinking that your project is inside
+<tt>llvm/trunk/projects/sample</tt>.</li>
<li>Add your source code and Makefiles to your source tree.</li>
<ul>
<li><b>AC_INIT</b>. Place the name of your project, its version number and
a contact email address for your project as the arguments to this macro</li>
- <li><b>AC_CONFIG_AUC_DIR</b>. If your project isn't in the
+ <li><b>AC_CONFIG_AUX_DIR</b>. If your project isn't in the
<tt>llvm/projects</tt> directory then you might need to adjust this so that
it specifies a relative path to the <tt>llvm/autoconf</tt> directory.</li>
<li><b>LLVM_CONFIG_PROJECT</b>. Just leave this alone.</li>
<li><b>AC_CONFIG_SRCDIR</b>. Specify a path to a file name that identifies
- your project; or just leave it at <tt>Makefile.config.in</tt></li>
+ your project; or just leave it at <tt>Makefile.common.in</tt></li>
<li><b>AC_CONFIG_FILES</b>. Do not change.</li>
<li><b>AC_CONFIG_MAKEFILE</b>. Use one of these macros for each Makefile
that your project uses. This macro arranges for your makefiles to be copied
<div class="doc_code">
<p><tt>% cd autoconf<br>
- % AutoRegen.sh</tt></p>
+ % ./AutoRegen.sh</tt></p>
</div>
-<p>You must be using Autoconf version 2.59 or later and your aclocal version
-should 1.9 or later.</p></li>
+<p>You must be using Autoconf version 2.59 or later and your aclocal version
+should be 1.9 or later.</p></li>
<li>Run <tt>configure</tt> in the directory in which you want to place
object code. Use the following options to tell your project where it
<dl>
<dt><tt>--with-llvmsrc=<directory></tt></dt>
<dd>Tell your project where the LLVM source tree is located.</dd>
- <dt><br/><tt>--with-llvmobj=<directory></tt></dt>
+ <dt><br><tt>--with-llvmobj=<directory></tt></dt>
<dd>Tell your project where the LLVM object tree is located.</dd>
- <dt><br/><tt>--prefix=<directory></tt></dt>
+ <dt><br><tt>--prefix=<directory></tt></dt>
<dd>Tell your project where it should get installed.</dd>
</dl>
</ol>
how to run the test. See the <a
href="TestingGuide.html">TestingGuide</a> for more details. You
can easily write Makefile support similar to the Makefiles in
- <tt>llvm/test</tt> to use Dejagnu to run your project's tests.<br/></li>
+ <tt>llvm/test</tt> to use Dejagnu to run your project's tests.<br></li>
<li>
LLVM contains an optional package called <tt>llvm-test</tt>
which provides benchmarks and programs that are known to compile with the
LLVM GCC front ends. You can use these
programs to test your code, gather statistics information, and
compare it to the current LLVM performance statistics.
- <br/>Currently, there is no way to hook your tests directly into the
+ <br>Currently, there is no way to hook your tests directly into the
<tt>llvm/test</tt> testing harness. You will simply
need to find a way to use the source provided within that directory
on your own.
<hr>
<address>
<a href="http://jigsaw.w3.org/css-validator/check/referer"><img
- src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
+ src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
<a href="http://validator.w3.org/check/referer"><img
- src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
+ src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
<a href="mailto:criswell@uiuc.edu">John Criswell</a><br>
<a href="http://llvm.org">The LLVM Compiler Infrastructure</a>
projects / oota-llvm.git / blobdiff