<div dir="rtl"><div dir="ltr">You only need to have the bin directory in your PATH. clang will find the include and library directory based on the bin directory. There are no fixed paths, you can put in c:\mingw or wherever.</div><div dir="ltr"><br></div><div dir="ltr"><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div dir="ltr">2015-07-03 16:13 GMT+03:00 Edward Diener <span dir="ltr"><<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a>></span>:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 6/25/2015 2:13 PM, Yaron Keren wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
See <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=ecMMp1TUmHLfiiZ_MlnPwTgmGQGZqkJoByqz4GWmOJ8&s=GyhTLhjqmvS-L0bXc8ytxxjhk6AnpKowj6eW2JYk9i4&e=" rel="noreferrer" target="_blank">http://reviews.llvm.org/D5268</a><br>
<<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=YgSrUuiAhPt76cF_h_LXb8Mg84W8p9nMvUiL3koHKP4&s=aW_6t6KDGfo5hO6NiTn5Hy9afNhzwfkX-BZHT9PtXmk&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=YgSrUuiAhPt76cF_h_LXb8Mg84W8p9nMvUiL3koHKP4&s=aW_6t6KDGfo5hO6NiTn5Hy9afNhzwfkX-BZHT9PtXmk&e=</a>><br>
</blockquote>
<br>
I can see that the patch has been applied officially to the latest clang source. It's in the latest code when I update llvm/clang. Thanks very much !<br>
<br>
But how do I use it ?<br>
<br>
Am I supposed to be able to build clang using a mingw-64 distro in my PATH ?<br>
<br>
When I compile with clang how do I tell it to use the mingw-64 headers and RTL ? Does it matter whether the mingw-64 distro is 32 bit or 64 bit ?<br>
<br>
Do I need to have the mingw-64 distro at c:\mingw ?<br>
<br>
I am willing to test this for clang and report back results here, since I can easily switch between mingw-64 distros ( 4.8.4, 4.9.2, 5.1 ) and I test a number of Boost libraries including my own with clang, but I need a little information on how to do it.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
<br>
<br>
<br>
2015-06-25 10:46 GMT+03:00 Edward Diener<br>
<<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a><br></span>
<mailto:<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a>>>:<div><div><br>
<br>
For either the latest clang built from souce on Windows or a binary<br>
distribution of clang on Windows it appears that clang expects the<br>
supporting gcc include files and lib files to be in the hardcoded<br>
directory:<br>
<br>
c:\mingw<br>
<br>
and follow the mingw directory structure.<br>
<br>
1) Can this please be changed in the future so that some environment<br>
variable ( maybe CLANG_GCC ) can be set to the gcc installation<br>
rather than use a hardcoded path ?<br>
<br>
2) Can clang be updated to support the mingw-64 directory structure<br>
and not just the mingw directory structure ? The mingw-64 distros<br>
seem now to be the preferred gcc distributions on Windows and<br>
support the latest versions of gcc.<br>
<br>
Do I need to make these suggestions on the clang bug tracker for the<br>
suggestions to be seriously considered ?u<br>
</div></div></blockquote><div><div>
<br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
</div></div></blockquote></div><br></div></div>