LLVM-CONFIG(1)

📦
version 15.0.7 · 7 versions
, in ubuntu jammy

💖 NAME 💖

okay so welcome to LLVM-CONFIG(1), bestie — this is llvm-config, the CLI that prints LLVM compilation options. It’s giving “build-system wingwoman” and honestly? iconic. 🫶

✨ SYNOPSIS ✨

llvm-config option [components…]

🌸 DESCRIPTION 🌸

llvm-config makes building applications that use LLVM way easier. It can print the compiler flags, linker flags, and object libraries you need to link against LLVM. Literally the “here’s what you need to link, no cap” bestie. 💅

🦋 EXAMPLES 🦋

To link against the JIT, you’d do this cute little two-step:

g++ `llvm-config --cxxflags` -o HowToUseJIT.o -c HowToUseJIT.cpp
g++ `llvm-config --ldflags` -o HowToUseJIT HowToUseJIT.o \
    `llvm-config --libs engine bcreader scalaropts`

💜 OPTIONS 💜

  • --assertion-mode — prints the assertion mode used when LLVM was built (ON or OFF). ✨
  • --bindir — prints the installation directory for LLVM binaries.
  • --build-mode — prints the build mode used when LLVM was built (e.g. Debug or Release).
  • --build-system — prints the build system used to build LLVM (e.g. cmake or gn).
  • --cflags — prints the C compiler flags needed to use LLVM headers.
  • --cmakedir — prints the installation directory for LLVM CMake modules.
  • --components — prints all valid component names. the ultimate roster reveal 🎀
  • --cppflags — prints the C preprocessor flags needed to use LLVM headers.
  • --cxxflags — prints the C++ compiler flags needed to use LLVM headers.
  • --has-rtti — prints whether or not LLVM was built with rtti (YES or NO).
  • --help — prints a summary of llvm-config arguments. bestie behavior.
  • --host-target — prints the target triple used to configure LLVM.
  • --ignore-libllvm — ignore libLLVM and link component libraries instead.
  • --includedir — prints the installation directory for LLVM headers.
  • --ldflags — prints the flags needed to link against LLVM libraries.
  • --libdir — prints the installation directory for LLVM libraries.
  • --libfiles — similar to --libs, but prints the full path to each library file. This is useful when creating makefile dependencies, to ensure that a tool is relinked if any library it uses changes. 🧚
  • --libnames — similar to --libs, but prints the bare filenames of the libraries without -l or pathnames. Useful for linking against a not-yet-installed copy of LLVM.
  • --libs — prints all the libraries needed to link against the specified LLVM components, including any dependencies. the main character of link flags, fr fr
  • --link-shared — link the components as shared libraries.
  • --link-static — link the component libraries statically.
  • --obj-root — prints the object root used to build LLVM.
  • --prefix — prints the installation prefix for LLVM.
  • --shared-mode — prints how the provided components can be collectively linked (shared or static).
  • --src-root — prints the source root from which LLVM was built.
  • --system-libs — prints all the system libraries needed to link against the specified LLVM components, including any dependencies.
  • --targets-built — prints the component names for all targets supported by this copy of LLVM. 🌈
  • --version — prints the version number of LLVM.

🎀 COMPONENTS 🎀

To print a list of all available components, run llvm-config --components. In most cases, components correspond directly to LLVM libraries. Useful “virtual” components include:

  • all — includes all LLVM libraries. The default if no components are specified.
  • backend — includes either a native backend or the C backend.
  • engine — includes either a native JIT or the bitcode interpreter.

⭐ EXIT STATUS ⭐

If llvm-config succeeds, it will exit with 0. Otherwise, if an error occurs, it will exit with a non-zero value. zero is the slay outcome, bestie. 💀

👑 AUTHOR 👑

Maintained by the LLVM Team (https://llvm.org/).

2003-2023, LLVM Project

that’s the whole page, bestie — from LLVM-CONFIG(1), version 15, dated 2023-07-14. now go link something iconic. 💅✨

📦 where this page comes from