[cfe-dev] Windows and Clang

[Russell Wallace via cfe-dev]

That's basically the configuration I'm using thus far too, so if there are
problems with it, I'd like to know about them in case they're problems I'm
going to run into in the near future! Why is that configuration not working
for you? What sort of errors are you getting?

I'm using Visual C++ 2015 and clang 3.7.0, with everything set to 64-bit,
is that the same as you have?

On Thu, Sep 3, 2015 at 10:54 AM, Joshua Gerrard <joshua.gerrard at roli.com>
wrote:

> Thanks for the quick reply!
>
> The project is compiled using MSVC at present, which in turn links against
> clang (compiled with MSVC), the Windows VC++ runtime libraries and uses
> Windows API calls. Internally, it compiles programs with clang for running
> on Windows that in turn use Windows API calls. You can think of the whole
> thing as a GUI wrapper around clang on Windows (it's a lot more than that,
> but that gives you an idea of how clang is being used).
>
> --
> Joshua Gerrard
> JUCE Software Developer
>
> The Seaboard GRAND is a breakthrough new musical instrument called “the
> piano of the future” (CNN) and “influential, innovative, and inspiring” and
> “ingenious” (Telegraph). With orders from 34 countries, the Seaboard GRAND
> is now shipping and available for sale at www.roli.com/seaboard
>
> Office: +44(0)207 254 2155
> Cell:    07885 557494
>
> ROLI
> 2 Glebe Road, London E8 4BD
> www.roli.com
>
> Discover more about us on Facebook - Twitter - Youtube
>
> ROLI Ltd. is a registered company in England and Wales, and this e-mail
> and its attachment(s) are intended for the above named only and are
> confidential. If they have come to you in error then you must take no
> action based upon them but contact us immediately. Any disclosure, copying,
> distribution or any action taken or omitted to be taken in reliance on it
> is prohibited and may be unlawful. Although this e-mail and its attachments
> are believed to be free of any virus, it is the responsibility of the
> recipient to ensure that they are virus free. If you contact us by e-mail
> then we will store your name and address to facilitate communications. Any
> statements contained herein are those of the individual and not the
> organisation.
>
>
> On 3 September 2015 at 10:45, Russell Wallace <russell.wallace at gmail.com>
> wrote:
>
>> My limited experience with clang on Windows thus far is that for most
>> purposes it is no longer necessary to use mingw. The linked page that
>> mentions it, does so specifically in the context of ABI compatibility, i.e.
>> some of your code is compiled with clang, some with another compiler using
>> at least moderately exotic C++ features and there is a need to link them
>> together. Does your project require that, or is it possible to do things
>> another way e.g. compile everything with clang?
>>
>> On Thu, Sep 3, 2015 at 10:16 AM, Joshua Gerrard via cfe-dev <
>> cfe-dev at lists.llvm.org> wrote:
>>
>>> Hey folks, apologies for the rather noobish email...
>>>
>>> I'd love to get into clang (and maybe llvm?) development, as some of my
>>> projects use it as a "black box" that I'd "unbox" that, to make it easier
>>> to debug if nothing else. At the moment, the project I'm working on works
>>> great on Mac OS X, but fails miserably for unknown reasons on Windows.
>>>
>>> I took a read of http://clang.llvm.org/docs/MSVCCompatibility.html and
>>> it recommended using mingw32 instead of MSVC where possible, but this would
>>> mean porting the (very large) project over so that it works on mingw32,
>>> which would take a large but doable amount of time.
>>>
>>> My question is, if I spend the time to get everything working on
>>> mingw32, is clang in a state to "mostly work" on Window after that
>>> (assuming my application code isn't doing anything stupid)? To be a little
>>> more specific, clang is being linked against to compile C++ code that is
>>> later run (i.e. it's not for static analysis). If mingw32 isn't in such a
>>> state, is the MSVC version? The link I posted above gives me some
>>> information about this, and I'm OK with only compiling for 64 bit (as the
>>> exception comments mention that 64 bit exceptions are in a decent state),
>>> but I don't know anything beyond what's in that article.
>>>
>>> Thank you very much for any help in advance!
>>>
>>> Regards,
>>>
>>> Joshua
>>>
>>> _______________________________________________
>>> cfe-dev mailing list
>>> cfe-dev at lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150903/8b6cf6dd/attachment.html>