Michael Kruse via llvm-dev
2021-Aug-03 15:21 UTC
[llvm-dev] building LLVM 11 with OpenMP on Windows
Am Di., 3. Aug. 2021 um 05:05 Uhr schrieb Geoff Levner via llvm-dev <llvm-dev at lists.llvm.org>:> Perhaps a solution would be to compile LLVM/Clang and OpenMP with Visual Studio but separately? Only I don't know how to do that...You could use ninja on Windows (-cmake GNinja) which only has a single configuration per builddir. If compilation with cl.exe fail, try LLVM_ENABLE_RUMTIMES=openmp (instead of LLVM_ENABLE_PROJECTS=openmp) which will build libomp using just-built clang. Michael
Geoff Levner via llvm-dev
2021-Aug-03 15:52 UTC
[llvm-dev] building LLVM 11 with OpenMP on Windows
Thanks for that, Michael. The workaround I have found for now is to use nmake and to avoid trace statements in OpenMP, which cause the compilation errors in the debug configuration, by commenting out the line in the OpenMP source code that #defines KMP_DEBUG to 1. But that is not a nice workaround. I will try setting LLVM_ENABLE_RUNTIMES, as you suggest, to see if that works without hacking the source code. (Also nmake is very, very slow. Presumably ninja will be faster.) On Tue, Aug 3, 2021 at 5:22 PM Michael Kruse <llvmdev at meinersbur.de> wrote:> Am Di., 3. Aug. 2021 um 05:05 Uhr schrieb Geoff Levner via llvm-dev > <llvm-dev at lists.llvm.org>: > > Perhaps a solution would be to compile LLVM/Clang and OpenMP with Visual > Studio but separately? Only I don't know how to do that... > > You could use ninja on Windows (-cmake GNinja) which only has a single > configuration per builddir. If compilation with cl.exe fail, try > LLVM_ENABLE_RUMTIMES=openmp (instead of LLVM_ENABLE_PROJECTS=openmp) > which will build libomp using just-built clang. > > Michael >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210803/71d26835/attachment.html>