<div dir="ltr">I'm using Visual Studio 2013 (just because we suppose it'll be better tested etc) with revision 245761 of clang, compiler-rt and llvm. I'm also using the ORC JIT engine to compile the C++ code.<div><br></div><div>The errors we're getting are non-deterministic, which is what is making it so hard to figure out.</div><div><br></div><div>Are you building the release from source, and if so, what cmake flags are you using? Any other things I should know about that you use to build your project? </div><div><br></div><div>Much appreciated as always,</div><div><br></div><div>Joshua</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><p dir="ltr">--<br> Joshua Gerrard<br> JUCE Software Developer<br></p><p dir="ltr"> 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 <a href="http://www.roli.com/seaboard" target="_blank"><font color="#1155cc">www.roli.com/seaboard</font></a><br></p><p dir="ltr">Office: <a href="tel:%2B44%280%29207%20254%202155" value="+442072542155" target="_blank"><font color="#1155cc">+44(0)207 254 2155</font></a><br> Cell: 07885 557494<br><br></p><p dir="ltr">ROLI<br> 2 Glebe Road, London E8 4BD<br><a href="http://www.roli.com/" target="_blank"><font color="#1155cc">www.roli.com</font></a><br></p><p dir="ltr">Discover more about us on Facebook - Twitter - Youtube</p><p dir="ltr">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.<br><br></p></div></div></div></div></div></div>
<br><div class="gmail_quote">On 3 September 2015 at 10:58, Russell Wallace <span dir="ltr"><<a href="mailto:russell.wallace@gmail.com" target="_blank">russell.wallace@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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?</div><div><br></div><div>I'm using Visual C++ 2015 and clang 3.7.0, with everything set to 64-bit, is that the same as you have?</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 3, 2015 at 10:54 AM, Joshua Gerrard <span dir="ltr"><<a href="mailto:joshua.gerrard@roli.com" target="_blank">joshua.gerrard@roli.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for the quick reply!<div><br><div>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).</div></div></div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><div><p dir="ltr">--<br> Joshua Gerrard<br> JUCE Software Developer<br></p><p dir="ltr"> 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 <a href="http://www.roli.com/seaboard" target="_blank"><font color="#1155cc">www.roli.com/seaboard</font></a><br></p><p dir="ltr">Office: <a href="tel:%2B44%280%29207%20254%202155" value="+442072542155" target="_blank"><font color="#1155cc">+44(0)207 254 2155</font></a><br> Cell: 07885 557494<br><br></p><p dir="ltr">ROLI<br> 2 Glebe Road, London E8 4BD<br><a href="http://www.roli.com/" target="_blank"><font color="#1155cc">www.roli.com</font></a><br></p><p dir="ltr">Discover more about us on Facebook - Twitter - Youtube</p><p dir="ltr">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.<br><br></p></div></div></div></div></div></div><div><div>
<br><div class="gmail_quote">On 3 September 2015 at 10:45, Russell Wallace <span dir="ltr"><<a href="mailto:russell.wallace@gmail.com" target="_blank">russell.wallace@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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?<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Thu, Sep 3, 2015 at 10:16 AM, Joshua Gerrard via cfe-dev <span dir="ltr"><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div dir="ltr"><div dir="ltr"><p>Hey folks, apologies for the rather noobish email...</p><p>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.</p><p>I took a read of <a href="http://clang.llvm.org/docs/MSVCCompatibility.html" target="_blank">http://clang.llvm.org/docs/MSVCCompatibility.html</a> 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.<br></p><p>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.</p><p>Thank you very much for any help in advance!</p><p>Regards,</p><p>Joshua</p></div></div></div></div>
</div>
<br></div></div>_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>