X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FUsingLibraries.html;h=af57907ef66a730bbc6977265999d2afb5a862fe;hb=963a97f1a365c8d09ca681e922371f9ec3473ee8;hp=9cb383d31c75db6acb539dfe75c3d7f4d4aa9672;hpb=d006d3a17a39d2861f1c63ba9090bdb77d033afa;p=oota-llvm.git diff --git a/docs/UsingLibraries.html b/docs/UsingLibraries.html index 9cb383d31c7..af57907ef66 100644 --- a/docs/UsingLibraries.html +++ b/docs/UsingLibraries.html @@ -23,7 +23,7 @@
Written by Reid Spencer
-Warning: This document is out of date, please see llvm-config for more information. +Warning: This document is out of date, please see llvm-config for more information.
@@ -33,8 +33,10 @@ Warning: This document is out of date, please see If you're writing a compiler, virtual machine, or any other utility based on LLVM, you'll need to figure out which of the many libraries files you will need to link with to be successful. An understanding of the contents of these - files and their inter-relationships will be useful in coming up with an optimal - specification for the libraries to link with. The purpose of this document is - to reduce some of the trial and error that the author experienced in using - LLVM. + libraries will be useful in coming up with an optimal specification for the + libraries to link with. The purpose of this document is to reduce some of + the trial and error that the author experienced in using LLVM.LLVM produces two types of libraries: archives (ending in .a) and objects (ending in .o). However, both are libraries. Libraries ending in .o are known as re-linked libraries because they contain all the compilation units of the library linked together as a single .o file. - Furthermore, many of the libraries have both forms of library. The + Furthermore, several of the libraries have both forms of library. The re-linked libraries are used whenever you want to include all symbols from the library. The archive libraries are used whenever you want to only resolve outstanding symbols at that point in the link without including everything in the library.
-When linking your tools, you will use the LLVMLIBS make variable. +
If you're using the LLVM Makefile system to link your tools,you will use
+ the LLVMLIBS make variable.
(see the Makefile Guide for
details). This variable specifies which LLVM libraries to link into your tool
and the order in which they will be linked. You specify re-linked libraries by
@@ -76,94 +78,107 @@ Warning: This document is out of date, please see Core Libraries
- LLVMArchive .a
LLVM archive reading and writing LLVMAsmParser .o
+
- LLVMAsmParser .a
LLVM assembly parsing
- LLVMBCReader .o
- LLVM bytecode reading
- LLVMBCWriter .o
- LLVM bytecode writing LLVMCore .o
+
+ LLVMBCReader .a
+ LLVM bitcode reading
+ LLVMBCWriter .a
+ LLVM bitcode writing
- LLVMCore .a
LLVM core intermediate representation LLVMDebugger .o
+ LLVMDebugger .a
Source level debugging support
- LLVMLinker .a
- Bytecode and archive linking interface
+ LLVMSupport .a .o
+ Bitcode and archive linking interface
- LLVMSupport .a
General support utilities LLVMSystem .a .o
+
+ LLVMSystem .a
Operating system abstraction layer LLVMbzip2 .a
+ BZip2 compression library
- Analysis Libraries LLVMAnalysis .a .o
+
- LLVMAnalysis .a
Various analysis passes. LLVMDataStructure .a .o
+
- LLVMDataStructure .o
Data structure analysis passes. LLVMipa .a .o
+ LLVMipa .a
Inter-procedural analysis passes.
- Transformation Libraries LLVMInstrumentation .a .o
+
- LLVMInstrumentation .a
Instrumentation passes. LLVMipo .a .o
+
- LLVMipo .a
All inter-procedural optimization passes. LLVMScalarOpts .a .o
+
- LLVMScalarOpts .a
All scalar optimization passes.
- LLVMTransforms .a .o
- Uncategorized transformation passes.
- LLVMTransformUtils .a .o
- Transformation utilities.
+ LLVMProfilePaths .o
- Profile paths for instrumentation. LLVMTransformUtils .a
+ Transformation utilities used by many passes. Code Generation Libraries
+ LLVMCodeGen .o
Native code generation infrastructure LLVMSelectionDAG .o
+ Aggressive instruction selector for directed acyclic graphs
+ Target Libraries
+ LLVMAlpha .o
+ Code generation for Alpha architecture LLVMARM .o
+ Code generation for ARM architecture
+ LLVMCBackend .o
'C' language code generator. LLVMIA64 .o
+ Code generation for IA64 architecture
- LLVMPowerPC .o
- PowerPC code generation backend
- LLVMSelectionDAG .o
- Aggressive instruction selector for directed acyclic graphs.
+ LLVMSkeleton .a .o
- Skeleton for a code generation backend.
Below are two dependency graphs and a list that show the relationships - between the various LLVM archive libraries and object files. This information - can be automatically generated with the GenLibDeps.pl utility found - in the llvm/utils directory.
+The llvm-config tool is a perl script that produces on its output + various kinds of information. For example, the source or object directories + used to build LLVM can be accessed by passing options to llvm-config. + For complete details on this tool, please see the + manual page.
+To understand the relationships between libraries, the llvm-config + can be very useful. If all you know is that you want certain libraries to + be available, you can generate the complete set of libraries to link with + using one of four options, as below:
+If you wish to delve further into how llvm-config generates the + correct order (based on library dependencies), please see the tool named + GenLibDeps.pl in the utils source directory of LLVM.
+ @@ -185,280 +200,208 @@ Warning: This document is out of date, please see