X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FProjects.html;h=ada6196be2a9f3f214002015288b3768ff175286;hb=a419b56d896d5180adb14e39d5c969306bd5b400;hp=afa33eee56a0df003b8420686be5ba8639629d40;hpb=623751fbecb588ef4b1ac3048ebfe064fb73066b;p=oota-llvm.git diff --git a/docs/Projects.html b/docs/Projects.html index afa33eee56a..ada6196be2a 100644 --- a/docs/Projects.html +++ b/docs/Projects.html @@ -88,10 +88,10 @@ choosing. You can place it anywhere you like. Rename the directory to match the name of your project.
  • -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 llvm/projects/sample. -
    • +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 +llvm/trunk/projects/sample.
  • Add your source code and Makefiles to your source tree.
    • @@ -105,7 +105,7 @@ then you need to edit autoconf/configure.ac as follows: it specifies a relative path to the llvm/autoconf directory.
  • LLVM_CONFIG_PROJECT. Just leave this alone.
  • AC_CONFIG_SRCDIR. Specify a path to a file name that identifies - your project; or just leave it at Makefile.config.in
    • + your project; or just leave it at Makefile.common.in
  • AC_CONFIG_FILES. Do not change.
  • AC_CONFIG_MAKEFILE. Use one of these macros for each Makefile that your project uses. This macro arranges for your makefiles to be copied @@ -118,11 +118,11 @@ configure script with these commands:

    % cd autoconf
    - % AutoRegen.sh

    + % ./AutoRegen.sh

    -

    You must be using Autoconf version 2.59 or later and your aclocal version -should 1.9 or later.

    • +

    You must be using Autoconf version 2.59 or later and your aclocal version +should be 1.9 or later.

  • Run configure in the directory in which you want to place object code. Use the following options to tell your project where it @@ -131,9 +131,9 @@ can find LLVM:
    --with-llvmsrc=<directory>
    Tell your project where the LLVM source tree is located.
    -

    --with-llvmobj=<directory>
    +

    --with-llvmobj=<directory>
    Tell your project where the LLVM object tree is located.
    -

    --prefix=<directory>
    +

    --prefix=<directory>
    Tell your project where it should get installed.
    @@ -210,14 +210,14 @@ directories:

    how to run the test. See the TestingGuide for more details. You can easily write Makefile support similar to the Makefiles in - llvm/test to use Dejagnu to run your project's tests.
    • + llvm/test to use Dejagnu to run your project's tests.
  • LLVM contains an optional package called llvm-test 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. -
    Currently, there is no way to hook your tests directly into the +
    Currently, there is no way to hook your tests directly into the llvm/test testing harness. You will simply need to find a way to use the source provided within that directory on your own. @@ -446,9 +446,9 @@ Mailing List.

    Valid CSS! + src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"> Valid HTML 4.01! + src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"> John Criswell
    The LLVM Compiler Infrastructure