X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FCMake.html;h=0bafedd9b0930254569a67348b90efe9fde7885c;hb=a75ce9f5d2236d93c117e861e60e6f3f748c9555;hp=606d3995af36f72e35555e6542624e7ef553b915;hpb=cbdbcb12fcde2ca5bc5b4a86307bb451abb0502b;p=oota-llvm.git diff --git a/docs/CMake.html b/docs/CMake.html index 606d3995af3..0bafedd9b09 100644 --- a/docs/CMake.html +++ b/docs/CMake.html @@ -67,8 +67,8 @@
Download - and install CMake. Version 2.6.2 is the minimum required.
+Download + and install CMake. Version 2.8 is the minimum required.
Open a shell. Your development tools must be reachable from this shell through the PATH environment variable.
@@ -180,7 +180,7 @@Variables are stored on the CMake cache. This is a file
- named
Variables are listed here appending its type after a colon. It is @@ -209,7 +209,7 @@
LLVM testing is not supported on Visual Studio.
+Testing is performed when the check target is built. For + instance, if you are using makefiles, execute this command while on + the top level of your build directory:
-TODO
+make check
+Testing is not supported on Visual Studio.
Also see the LLVM-specific variables + section for variables used when cross-compiling.
+ @@ -314,7 +391,38 @@TODO
+The most difficult part of adding LLVM to the build of a project + is to determine the set of LLVM libraries corresponding to the set + of required LLVM features. What follows is an example of how to + obtain this information:
+ ++ # A convenience variable: + set(LLVM_ROOT "" CACHE PATH "Root of LLVM install.") + # A bit of a sanity check: + if( NOT EXISTS ${LLVM_ROOT}/include/llvm ) + message(FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM install") + endif() + # We incorporate the CMake features provided by LLVM: + set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${LLVM_ROOT}/share/llvm/cmake") + include(LLVM) + # Now set the header and library paths: + include_directories( ${LLVM_ROOT}/include ) + link_directories( ${LLVM_ROOT}/lib ) + # Let's suppose we want to build a JIT compiler with support for + # binary code (no interpreter): + llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) + # Finally, we link the LLVM libraries to our executable: + target_link_libraries(mycompiler ${REQ_LLVM_LIBRARIES}) ++
This assumes that LLVM_ROOT points to an install of LLVM. The + procedure works too for uninstalled builds although we need to take + care to add an include_directories for the location of the + headers on the LLVM source directory (if we are building + out-of-source.)
For linking the JIT into your executable, add
- -/INCLUDE:_X86TargetMachineModule
-to your linker options. This is required for adding the relevant - LLVM object code to the executable. Not doing this will result on - some methods returning NULL (ExecutionEngine::create, for - instance).
- -