| Issue |
61649
|
| Summary |
LLVM_ENABLE_PROJECTS & LLVM_ENABLE_RUNTIMES should be disjoint, yet openmp is listed in both?
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
bjodah
|
I'm building llvm from source, and I'm a bit confused by the documentation of the cmake options:
>From https://llvm.org/docs/CMake.html, emphasis (bold) is mine
<dl>
<dt>LLVM_ENABLE_PROJECTS:STRING</dt>
<dd>Semicolon-separated list of projects to build, or all for building all (clang, lldb, lld, polly, etc) projects. This flag assumes that projects are checked out side-by-side and not nested, i.e. clang needs to be in parallel of llvm instead of nested in llvm/tools. This feature allows to have one build for only LLVM and another for clang+llvm using the same source checkout. The full list is: clang;clang-tools-extra;cross-project-tests;libc;libclc;lld;lldb;<b>openmp</b>;polly;pstl</dd>
<dt>LLVM_ENABLE_RUNTIMES:STRING</dt>
<dd>Build libc++, libc++abi, libunwind or compiler-rt using the just-built compiler. This is the correct way to build runtimes when putting together a toolchain. It will build the builtins separately from the other runtimes to preserve correct dependency ordering. If you want to build the runtimes using a system compiler, see the [libc++ documentation](https://libcxx.llvm.org/BuildingLibcxx.html). Note: the list <b>should not have duplicates with LLVM_ENABLE_PROJECTS</b>. The full list is: compiler-rt;libc;libcxx;libcxxabi;libunwind;<b>openmp</b> To enable all of them, use: LLVM_ENABLE_RUNTIMES=all</dd>
</dl>
I get the impression that openmp runtime is perhaps different from the openmp "compiler"? Either way I think the docs could be improved here, would you agree?
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
