[cfe-dev] [LLVMdev] [RFC] Raising LLVM minimum required MSVC version to 2013 for trunk
bayoubengal at mac.com
Mon Aug 25 08:29:46 PDT 2014
I have a dumb question...
How many actual known instances of alleged broken lines are there in the entire Microsoft API header stack?
If one had the dream of just fixing the headers, how big of a job would it actually be?
Sent from my iPad
> On Aug 24, 2014, at 3:56 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:
> Alex Rosenberg <alexr at leftfield.org> writes:
>>> On Aug 24, 2014, at 5:08 AM, Renato Golin <renato.golin at linaro.org> wrote:
>>>> On 24 August 2014 02:05, Alex Rosenberg <alexr at leftfield.org> wrote:
>>>> But it must. If you want to be able to use LLVM DLLs inside a
>>>> Windows app, it has to be built with MSVC because they have their
>>>> own C++ ABI. At some point, Clang will support Microsoft's ABI well
>>>> enough to consider a bootstrap instead.
>>> Ah, there's my answer! I thought we were at that stage already.
>> While admirable progress has been made, AFAIK, no attempt has begun to
>> get debugging working. It is not practical to use LLVM from within a
>> Windows application today unless it's built with MSVC.
> You mean "a Windows C++ application compiled by MSVC", don't you? (And
> even so we are ignoring the C bindings!)
> LLVM always was more usable with MinGW than with MSVC. That's a natural
> consequence of LLVM/Clang being focused on GCC compatibility and
> developed on a POSIX environment.
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
More information about the cfe-dev