1f75f318ae
In some situations such as reported at https://github.com/llvm/llvm-project/pull/177953#issuecomment-4179014239, LLVM_(DEFAULT_)TARGET_TRIPLE is not set. It is used to derive the output directory in #177953. Only flang-rt currently uses RUNTIMES_(INSTALL|OUTPUT)_RESOURCE_LIB_PATH, we should not fail building other despite a missing LLVM_TARGET_TRIPLE. Compiler-rt uses COMPILER_RT_DEFAULT_TARGET_TRIPLE instead which it derives itself. Most other LLVM runtimes libraries just skip the target portion of the library path (explicitly so since #93354). Do the same for RUNTIMES_(INSTALL|OUTPUT)_RESOURCE_LIB_PATH which we hope eventually can replace the other mechanisms.
The LLVM Compiler Infrastructure
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called "LLVM". This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Getting the Source Code and Building LLVM
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Getting in touch
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.