Llvm mingw #1173
Llvm mingw #1173
Conversation
When using libstdc++, it's somehow implicitly included, but it's not the case for libc++.
…pported before using it. lld-link linker does not support nor need it.
|
Maybe better use separate cross-files? More freedom to unconditionally set compiler binary names ( |
|
I don't see how it would be better. In my opinion, build system should be able to figure it out instead of hardcoding every possible configuration. |
ghost
deleted the
|
Sure, it completely on developers how to configure their project's build system, but in theory in such cross-files we configuring build environment only once. Then we should be able to build every similar project using the same cross-file, w/o any modification to build system. Those files even not needed to be a part of the project (meson can find them in In real world we have multiple similar projects with copy-pasted cross-files and meson.build. Many of them (projects) took DXVK's build system as template, and now they may feel like they should adjust their build systems in the similar way for llvm-mingw, but they shouldn't (IMHO). I personally would like to see this cross-files as a hint, to be moved in separate directory and extended with "debug" variants, even if I use completely different variant locally. Anyway, not a big deal. |
Fixes for compilation with llvm-mingw:
https://github.com/mstorsjo/llvm-mingw