From 502106a713f0e58700065161b2017bb57a6846df Mon Sep 17 00:00:00 2001 From: Mikhail Glushenkov Date: Tue, 16 Jun 2009 00:14:20 +0000 Subject: Regenerate. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@73449 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CompilerDriverTutorial.html | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) (limited to 'docs/CompilerDriverTutorial.html') diff --git a/docs/CompilerDriverTutorial.html b/docs/CompilerDriverTutorial.html index a578017379..897f9a9f89 100644 --- a/docs/CompilerDriverTutorial.html +++ b/docs/CompilerDriverTutorial.html @@ -50,21 +50,25 @@ command-line LLVMC usage, refer to the Using LLVMC to generate toolchain drivers

LLVMC plugins are written mostly using TableGen, so you need to be familiar with it to get anything done.

-

Start by compiling plugins/Simple/Simple.td, which is a primitive -wrapper for gcc:

+

Start by compiling example/Simple, which is a primitive wrapper for +gcc:

 $ cd $LLVM_DIR/tools/llvmc
-$ make DRIVER_NAME=mygcc BUILTIN_PLUGINS=Simple
+
+  # NB: A less verbose way to compile standalone LLVMC-based drivers is
+  # described in the reference manual.
+
+$ make LLVMC_BASED_DRIVER_NAME=mygcc LLVMC_BUILTIN_PLUGINS=Simple
 $ cat > hello.c
 [...]
 $ mygcc hello.c
 $ ./hello.out
 Hello
-

Here we link our plugin with the LLVMC core statically to form an -executable file called mygcc. It is also possible to build our -plugin as a standalone dynamic library; this is described in the -reference manual.

+

Here we link our plugin with the LLVMC core statically to form an executable +file called mygcc. It is also possible to build our plugin as a dynamic +library to be loaded by the llvmc executable (or any other LLVMC-based +standalone driver); this is described in the reference manual.

Contents of the file Simple.td look like this:

 // Include common definitions
-- 
cgit v1.2.3-18-g5258