This way, we could use it for LLVM_ENABLE_PROJECTS too if desired.
Details
- Reviewers
phosek jdoerfert - Group Reviewers
Restricted Project Restricted Project - Commits
- rG06400a0142af: [runtimes] Generalize how we reorder projects
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
runtimes/CMakeLists.txt | ||
---|---|---|
16 | I searched for if(TARGET asan) and we don't seem to use that anywhere so I'm not sure if this comment is still true. It's possible that this is outdated and we no longer need to do this. compiler-rt can depend on libcxx so I think it would make more sense to put compiler-rt after libcxx, we just need to check that nothing breaks if we do that. | |
19 | I think that libc and libunwind should come before libcxxabi and libcxx since that matches how these libraries are layered. |
runtimes/CMakeLists.txt | ||
---|---|---|
25 | This patch makes it impossible to build llvm-libgcc because LLVM_ALL_RUNTIMES deliberately doesn't include llvm-libgcc. I think this can be fixed by changing the first parameter to "${LLVM_ALL_RUNTIMES};llvm-libgcc", or by adding a variable that genuinely has all the runtimes (in reality, that would be spelt LLVM_ALL_RUNTIMES, and the current LLVM_ALL_RUNTIMES becomes LLVM_USER_ALL_RUNTIMES). |
I searched for if(TARGET asan) and we don't seem to use that anywhere so I'm not sure if this comment is still true. It's possible that this is outdated and we no longer need to do this.
compiler-rt can depend on libcxx so I think it would make more sense to put compiler-rt after libcxx, we just need to check that nothing breaks if we do that.