<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Reid,<br>
<br>
Thanks for the reply. Comments inline below.<br>
<br>
Regards,<br>
Eric<br>
<br>
<div class="moz-cite-prefix">On 9/29/14, 5:51 PM, Reid Kleckner
wrote:<br>
</div>
<blockquote
cite="mid:CACs=ty+PpWR0j6_sdnkHAXPhbQsm-vOfZecHdWJKriQ4RVcYwg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>I think any port will involve some changes, but it's really
hard to say which porting approach will be the least painless
beforehand. Aside from _MSC_VER incompatibilities messing up
portability headers, I think any changes you make to support
clang on Windows you would also have to do in order to use
MSVC. MinGW is another possible compiler, but then you're
porting to gcc, which is a different amount of work.<br>
</div>
</div>
</blockquote>
One of the things I'm hoping to gain from this approach is the
ability to directly compile Objective-C code. I'll try that today
and see what happens. I'm also hoping that Objective-C mixed in with
C++ will work, but perhaps _MSC_VER will mean that won't work?<br>
<blockquote
cite="mid:CACs=ty+PpWR0j6_sdnkHAXPhbQsm-vOfZecHdWJKriQ4RVcYwg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">I think you can turn of the _MSC_VER
definition with -fmsc-version= or some other flag, if you
want to try that. I wouldn't recommend it, because windows.h
and other system headers usually need to have _MSC_VER
defined.</div>
</div>
</div>
</blockquote>
Yes, that makes sense.<br>
<blockquote
cite="mid:CACs=ty+PpWR0j6_sdnkHAXPhbQsm-vOfZecHdWJKriQ4RVcYwg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">I saw your other thread about
installation troubles, but it's hard to debug remotely and I
didn't have time today to respond. It sounds like you got
that worked out?</div>
</div>
</div>
</blockquote>
I got it worked out by copying the x86 toolset files by hand. I
don't know why the installer, or install.bat couldn't write them -
install.bat finished without any error messages.<br>
<blockquote
cite="mid:CACs=ty+PpWR0j6_sdnkHAXPhbQsm-vOfZecHdWJKriQ4RVcYwg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Sep 29, 2014 at 8:08 PM, Eric
Mader <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:emader@gmx.us" target="_blank">emader@gmx.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I'm
trying to port a bunch of code from MacOS X to Windows.
The code is a mixture of C, C++11 and Objective-C. (Some
of the C++ code has bits of Objective-C mixed in, just for
spice ;-) Since it builds on the Mac with clang, I thought
that building on Windows with clang would mean that I
wouldn't have to make a bunch of changes just related to a
different compiler. For example, if I do a straight port
using Visual Studio, I have the replace all the uses of
blocks with either callbacks or lambdas.<br>
<br>
Having spent a couple of hours on this, I'm now wondering
if perhaps it's not as straight-forward as I thought. For
example, the toolset.props file adds the
-fmsc-version=1800 compiler flag, which fools the
conditional compilation in my header files into acting
just like they do with the Visual Studio compiler. Also,
I'm seeing an error where different header files have
different ideas about the type of t_size, but that my just
be something I have to fix.<br>
<br>
So, bottom line. Is my assumption that using clang on
Windows would simplify the porting process a valid one?<br>
<br>
Regards,<br>
Eric Mader<br>
<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a moz-do-not-send="true"
href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a>
<a moz-do-not-send="true"
href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a moz-do-not-send="true"
href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev"
target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>