Additionally I also build sanitizers and others with clang-cl for i386,x86 and aarch64. I use a MinGW sysroot that is already prebuilt (with GCC in my case) therefore only needing all the other runtimes to be built by clang. That setup has worked fine for me in some initial testing. DLLVM_ENABLE_PROJECTS="libunwind libcxxabi libcxx". #Cmake install for mingw seriesyou set the cmake configuration yourself, instead of instructing the machinery to figure it out based on a target triple), but you can add a series of projects to build as e.g. With that one, you configure building the runtimes just like a normal standalone project (i.e. #Cmake install for mingw how toThere's also a separate contender for how to build runtimes (still not entirely formally supported), as a middle ground - see. llvm/cmake/modules/LLVMExternalProjectUtils.cmake So therefore all of this is a bit of uncharted territory for me. For now I just build all of those subprojects individually afterwards. the mingw crt) between building the compiler and the rest of the llvm provided runtimes. In such cases, afaik the runtimes build is a bit tricky, because I'd need to build other bits (e.g. with no preexisting build tools first building the compiler, then building the base mingw crt, the compiler-rt builtins on top of that, and then other runtimes like libunwind, libcxxabi and libcxx on top of that. Windows is in the unique position of having two drivers, clang-cl and normal GNU clang, depending on whether a GNU or MSVC target is used.įWIW, the normal GNU frontend also works for the MSVC target some finer details are omitted in that case, but it rougly does work (and if the default target of the build is an msvc target, that's what targeted when calling that frontend too).Īlso FWIW, I haven't really used the runtimes build mechanism at all, because I primarily bootstrap everything from scratch in a cross compile setup, i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |