Refresh Makefile.ocaml in objdir if it is modified in srcdir.

[oota-llvm.git] / docs / Projects.html

diff --git a/docs/Projects.html b/docs/Projects.html
index c7ab6cf0263a5807330fdef15c95a475344b84e3..cb7a7c1bcfaa72df570532d54f6321760f9f9378 100644 (file)
--- a/docs/Projects.html
+++ b/docs/Projects.html
@@ -87,6 +87,12 @@ provide enough information on how to write your own Makefiles.</p>
 choosing.  You can place it anywhere you like.  Rename the directory to match
 the name of your project.</li>
 
+<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>
 
 <li>If you want your project to be configured with the <tt>configure</tt> script
@@ -94,12 +100,12 @@ then you need to edit <tt>autoconf/configure.ac</tt> as follows:
   <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</tt>. 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
@@ -203,19 +209,15 @@ directories:</p>
     test procedure uses RUN lines in the actual test case to determine
     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.</li>
-
-    <p>
-
+    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>
     <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.
-    <p>
-    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.
@@ -449,7 +451,7 @@ Mailing List</a>.</p>
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
 
   <a href="mailto:criswell@uiuc.edu">John Criswell</a><br>
-  <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
+  <a href="http://llvm.org">The LLVM Compiler Infrastructure</a>
   <br>
   Last modified: $Date$
 </address>