Repository files navigation

This directory and its sub-directories contain source code for LLVM,a toolkit for the construction of highly optimized compilers,optimizers, and run-time environments.

The README briefly describes how to get started with building LLVM.For more information on how to contribute to the LLVM project, pleasetake a look at theContributing to LLVM guide.

Taken fromhttps://llvm.org/docs/GettingStarted.html.

Welcome to the LLVM project!

The LLVM project has multiple components. The core of the project isitself called "LLVM". This contains all of the tools, libraries, and headerfiles needed to process intermediate representations and converts it intoobject files. Tools include an assembler, disassembler, bitcode analyzer, andbitcode optimizer. It also contains basic regression tests.

C-like languages use theClang front end. Thiscomponent compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode-- and from there into object files, using LLVM.

Other components include:thelibc++ C++ standard library,theLLD linker, and more.

The LLVM Getting Started documentation may be out of date. TheClangGetting Started page might have moreaccurate information.

This is an example work-flow and configuration to get and build the LLVM source:

1. Checkout LLVM (including related sub-projects like Clang):

   • git clone https://github.com/llvm/llvm-project.git

   • Or, on windows,git clone --config core.autocrlf=false https://github.com/llvm/llvm-project.git

2. Configure and build LLVM and Clang:

   • cd llvm-project

   • mkdir build

   • cd build

   • cmake -G <generator> [options] ../llvm

     Some common build system generators are:

     • Ninja --- for generatingNinjabuild files. Most llvm developers use Ninja.
     • Unix Makefiles --- for generating make-compatible parallel makefiles.
     • Visual Studio --- for generating Visual Studio projects andsolutions.
     • Xcode --- for generating Xcode projects.

     Some Common options:

     • -DLLVM_ENABLE_PROJECTS='...' --- semicolon-separated list of the LLVMsub-projects you'd like to additionally build. Can include any of: clang,clang-tools-extra, libcxx, libcxxabi, libunwind, lldb, compiler-rt, lld,polly, or debuginfo-tests.

       For example, to build LLVM, Clang, libcxx, and libcxxabi, use-DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi".

     • -DCMAKE_INSTALL_PREFIX=directory --- Specify fordirectory the fullpath name of where you want the LLVM tools and libraries to be installed(default/usr/local).

     • -DCMAKE_BUILD_TYPE=type --- Valid options fortype are Debug,Release, RelWithDebInfo, and MinSizeRel. Default is Debug.

     • -DLLVM_ENABLE_ASSERTIONS=On --- Compile with assertion checks enabled(default is Yes for Debug builds, No for all other build types).

   • cmake --build . [-- [options] <target>] or your build system specified abovedirectly.

     • The default target (i.e.ninja ormake) will build all of LLVM.

     • Thecheck-all target (i.e.ninja check-all) will run theregression tests to ensure everything is in working order.

     • CMake will generate targets for each tool and library, and mostLLVM sub-projects generate their owncheck-<project> target.

     • Running a serial build will beslow. To improve speed, try running aparallel build. That's done by default in Ninja; formake, use the option-j NNN, whereNNN is the number of parallel jobs, e.g. the number ofCPUs you have.

   • For more information seeCMake

Consult theGetting Started with LLVMpage for detailed information on configuring and compiling LLVM. You can visitDirectory Layoutto learn about the layout of the source code tree.