<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 23-5-2014 9:39, Ruben Van Boxem wrote:<br>
<blockquote
cite="mid:CALc40c-EzL18X+QJm3jTzBnKkpBgJW2Ln7EN4dBvwijxA--_CQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Hi Johan,<br>
<br>
</div>
The Driver merge request is located here:<br>
<a moz-do-not-send="true" href="http://reviews.llvm.org/D3420">http://reviews.llvm.org/D3420</a><br>
<br>
</div>
<div>It was not submitted by me, but has seen little activity
lately :-( I would say the patch more or less applies cleanly
and should work, although I myself haven't taken a very close
look at the modifications. Try it out, and let us know if
something doesn't work. I wrote the original Driver code based
on a personal GCC build (with default options) and the Arch
MinGW-w64 cross toolchain. So your mileage may vary.<br>
<br>
</div>
</div>
</blockquote>
<br>
Hi Ruben,<br>
It took a while but I finally looked at the patch. It almost
works. :-)<br>
It applies cleanly and compiles fine. But it does not search/find
the correct folders (for the MinGW-W64-builds download at least).
The C++ search paths do not include the GCC version in that package,
in contrast to what the mingw driver patch is searching for.<br>
<br>
I have added code to the merge request that makes it work for me.<br>
<a class="moz-txt-link-freetext" href="http://reviews.llvm.org/D3420#12">http://reviews.llvm.org/D3420#12</a><br>
<br>
Please have a look. I am not familiar with how to properly modify
the merge request.<br>
<br>
Thanks for the trouble. Again, it would be great if the next release
would have easier support for mingw64.<br>
<br>
Johan<br>
<br>
<br>
<br>
<blockquote
cite="mid:CALc40c-EzL18X+QJm3jTzBnKkpBgJW2Ln7EN4dBvwijxA--_CQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Ruben<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-05-23 1:32 GMT+02:00 Nikola
Smiljanic <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:popizdeh@gmail.com" target="_blank">popizdeh@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi Johan, I think that we're trying to move
away from logic in InitHeaderSearch. The idea is to
implement MinGW toolchain and the same way we have
Windows, GCC and other toolchains. Last thing I heard
Ruben was working on this (+CC)
<div>
<br>
</div>
Search for thread titled "Clang and (cross-)compilation
to [i686, x86_64]-w64-mingw32" on the mailing list for
more info.</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, May 23, 2014 at 8:56
AM, Johan Engelen <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jbc.engelen@swissonline.ch"
target="_blank">jbc.engelen@swissonline.ch</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
all,<br>
To make clang++ work (easily) with the latest
mingw-w64 builds by the Mingw-build project, I added
more paths to the search for default include
directories, and it works splendid. See the attached
patch.<br>
In short, the issue is that clang is searching for
versioned paths, but (at least for the package with
gcc4.9.0) the C++ include paths aren't versioned.
For example, right now, clang is searching for<br>
[...]/include/c++/4.8.0<br>
while really this folder is<br>
[...]/x86_64-w64-mingw32/include/c++<br>
<br>
Are you happy to add the following paths to the
default list?<br>
<sysroot>/x86_64-w64-mingw32/include/c++/<br>
<sysroot>/x86_64-w64-mingw32/include/c++/x86_64-w64-mingw32<br>
<sysroot>/x86_64-w64-mingw32/include/c++/backward<br>
<sysroot>/i686-w64-mingw32/include/c++/<br>
<sysroot>/i686-w64-mingw32/include/c++/i686-w64-mingw32<br>
<sysroot>/i686-w64-mingw32/include/c++/backward<br>
(the final 3 are a guess, judging from the symmetry
in the pathnames that clang already searches for)<br>
This assumes gcc and clang are in
<sysroot>/bin.<br>
I believe it will make life much easier for Windows
developers who want to give clang a spin.<br>
<br>
If so, I will clean up the modifications and submit
it for review.<br>
<br>
Thanks,<br>
Johan<br>
<br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
<a moz-do-not-send="true"
href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev"
target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>