Folks,
I have seen this line in llvm/CMakeLists.txt:
set(LLVM_ALL_PROJECTS "bolt;clang;clang-tools-extra;compiler-rt;cross-project-tests;libc;libclc;lld;lldb;mlir;openmp;polly;pstl")
# The flang project is not yet part of "all" projects (see C++ requirements)
set(LLVM_EXTRA_PROJECTS "flang")
Flang is not yet part of the list of "first-class LLVM projects. Could we move it over from LLVM_EXTRA_PROJECTS to LLVM_ALL_PROJECTS? That would solve a whole bunch of dependency issues that we are facing, when a runtime needs Flang to be available as a compiler before the runtime is being built.
What are the C++ requirements that might hinder the move? Flang uses C++17 (AFAIK), so do the remaining parts of LLVM.
Kind regards,
-michael
1 Like
I don’t have a strong opinion. FYI, This was last discussed in ⚙ D154109 Moved flang to LLVM_ALL_PROJECTS.
As per the discussion in the Flang/OpenMP call today, I will implement a different way to inject the proper build dependency in CMake and mark it as a TODO.
With the quoted link, this decision is beyond the PR that I’m working on and should be handled elsewhere (maybe even through the community process).
Isn’t that a remnant from a time when flang used C++17 and the rest of LLVM was still on C++14?
What would be right process to trigger the community decision for this one?
I’d post an RFC in the llvm-project section. And I’d give it a longer title. 
I understood from the OpenMP call today that Kiran will revive the discussion about this with the right folks.
PS: Cannot change the title, so it will remain short 