X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FProjects.html;h=cb7a7c1bcfaa72df570532d54f6321760f9f9378;hb=f368dadd9425de65fea4283daef5d197e98cc1cd;hp=db1838d5c8811523679b17716923b0b9950b43db;hpb=d967c80d642af0e2e1679df88ce8d93cc982b298;p=oota-llvm.git diff --git a/docs/Projects.html b/docs/Projects.html index db1838d5c88..cb7a7c1bcfa 100644 --- a/docs/Projects.html +++ b/docs/Projects.html @@ -87,41 +87,60 @@ provide enough information on how to write your own Makefiles.

choosing. You can place it anywhere you like. Rename the directory to match the name of your project. +
  • +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.
    • -
  • If you want your Makefiles to be configured by the configure -script, or if you want to support multiple object directories, add your -Makefiles to the configure script by adding them into the -autoconf/configure.ac file. The macro AC_CONFIG_MAKEFILE will -copy a file, unmodified, from the source directory to the object directory.
    • +
  • If you want your project to be configured with the configure script +then you need to edit autoconf/configure.ac as follows: + +
  • After updating autoconf/configure.ac, regenerate the configure script with these commands:

    % cd autoconf
    - % autoconf -o ../configure

    + % AutoRegen.sh

    -

    You must be using Autoconf version 2.57 or higher.

    • +

    You must be using Autoconf version 2.59 or later and your aclocal version +should 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 can find LLVM:
    -
    --with-llvmsrc=<directory> -
    - Tell your project where the LLVM source tree is located. -

    -

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

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

    --prefix=<directory>
    +
    Tell your project where it should get installed.
    -

    That's it! Now all you have to do is type gmake in the root of -your object directory, and your project should build.

    +

    That's it! Now all you have to do is type gmake (or make +if your on a GNU/Linux system) in the root of your object directory, and your +project should build.

    @@ -190,19 +209,15 @@ directories:

    test procedure uses RUN lines in the actual test case to determine 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.
    • - -

    - + can easily write Makefile support similar to the Makefiles in + 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. @@ -436,7 +451,7 @@ Mailing List.

    src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /> John Criswell
    - The LLVM Compiler Infrastructure + The LLVM Compiler Infrastructure
    Last modified: $Date$