<div dir="rtl"><div dir="ltr">clang with MingW is very similar to the other platforms, while clang-cl understands a whole different set of flags, the Visual C++ ones. Thus, you can have a clang toolset for all platforms while clang-cl lives in the Visual C++ toolset.</div>
<div dir="ltr"><br></div><div dir="ltr">Yaron</div><div dir="ltr"><br></div><div dir="ltr"><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div dir="ltr">2014-07-08 22:21 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"><div class="">On 7/8/2014 1:29 PM, Yaron Keren wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You can create two Windows configurations, one for clang.exe and one for<br>
clang-cl.exe.<br>
These are actually identical but the if I'm not mistaken the driver<br>
behaves differently based on the executable name.<br>
So you have "clang" and "clang-cl" toolsets.<br>
</blockquote>
<br></div>
That was an early thought but complicates the elegance of having a single Boost Build toolset for clang across Mac, Linux, and Windows.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
<br>
Yaron<br>
<br>
<br>
<br>
2014-07-08 18:13 GMT+03:00 Nico Weber <<a href="mailto:thakis@chromium.org" target="_blank">thakis@chromium.org</a><br></div>
<mailto:<a href="mailto:thakis@chromium.org" target="_blank">thakis@chromium.org</a>>>:<div class=""><br>
<br>
On Tue, Jul 8, 2014 at 6:54 AM, Edward Diener<br>
<<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.<u></u>com</a><br></div><div><div class="h5">
<mailto:<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@<u></u>tropicsoft.com</a>>> wrote:<br>
<br>
Since the two versions for clang on Windows, one using VC++ RTL<br>
and emulating VC++ to some small extent and the other using<br>
mingw rtl, are radically different, is there any easy way to<br>
distinguish between them at pre-execution time.<br>
<br>
In Boost Build we currently have a single toolset named 'clang'<br>
for the clang compiler. On Linux it uses a clang-linux.jam file,<br>
on the Mac it uses a clang-darwin.jam file, and I am trying to<br>
establish .jam files for using clang on Windows. Essentially I<br>
can use the clang-linux.jam file with a slight modification if<br>
the clang version uses mingw, but I need to use a clang-win.jam<br>
file if the clang version uses VC++. So somewhere early in the<br>
Boost Build processing I have to determine which 'clang.exe' is<br>
being used on Windows in order to invoke the proper Boost Build<br>
jam file for it.<br>
<br>
<br>
It's not really to different clang binaries as far as I know, just<br>
the same binary with a different default triple. So you could pass<br>
an explicit -target parameter to force one compiler behavior over<br>
the other too. (-target i386-pc-win32 for VC mode,<br>
-target i386-pc-mingw32 for gcc mode)<br>
<br>
<br>
Ideas ? Suggestions ?<br>
</div></div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<u></u>_________________<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" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/cfe-dev</a><br>
</div></div></blockquote></div><br></div>