<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi Juanjo,</span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">On Sun, Jun 23, 2013 at 3:09 AM, Juan Jose Garcia-Ripoll <span dir="ltr"><<a href="mailto:juanjose.garciaripoll@gmail.com" target="_blank">juanjose.garciaripoll@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="im"><br>
<div class="gmail_quote">On Sat, Jun 22, 2013 at 10:41 AM, Dietrich Bollmann <span dir="ltr"><<a href="mailto:dietrich@formgames.org" target="_blank">dietrich@formgames.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>Do I misunderstand the meaning of :WIN32?</div><div></div></blockquote></div><br></div><div class="im">This feature is related to the OS API that is used Win32 vs Mingw32 vs Cygwin32. On Windows64 the API used is still Win32, IIRC. I do not know how to change this without breaking some code out there, or whether the present situation is sensible or not. Maybe we coud at least push also Win64</div>
</div></div></blockquote><div><br></div><div>Thanks! So I misunderstood the meaning of :win32 in the *features* list :)</div><div><br></div><div>The reason is that I try to integrate ECL with Rhino3d and the latter complained about the compiler option 'WIN32' in combination with other 64bit options when compiling with 'asdf:make-build'. Also, when searching for win32 on the internet, it is nearly always used in opposition to win64 and as compiler option. But as you wrote in your email, in a different context it seems to be used as name for the windows API as well. What a confusing and unfortunate choice for a naming scheme!</div>
<div><br></div><div>By the way, Rhino3D also complains when both, 'win32' and 'win64' are set. This probably is caused by a similar confusion on their side. At least when believing the notes on the page "Compiler Constants" setting both seems to be the normal case ( <a href="http://msdn.microsoft.com/en-us/library/office/gg264614.aspx" target="_blank">http://msdn.microsoft.com/en-us/library/office/gg264614.aspx</a> ; this page is about the usage of these constants in visual basic but I suppose that it is valuable for c++ as well):</div>
<div><div><br></div><div>> Because Win32 returns true in both 32-bit and 64-bit development platforms it is important that the order within the #If...Then...#Else directive returns the desired results in your code. For example, because Win32 returns True in 64-bit (Win32is compatible in Win64 environments) checking for Win32 before Win64 results in the Win64 condition never running becauseWin32 returns True. </div>
<div><br></div><div>So maybe pushing win64 as well would be the right solution.</div><div><br></div><div>I wish Microsoft had made a less ambiguous choice, for example 'mswinapi' together with '32bit' and '64bit'. But it seems that the current situation results from historical reasons and that win32 can still be used in order to make the porting of applications from 32 bit to 64 bit easier. Not sure if not the opposite is the result though...</div>
<div><br></div><div>Thanks again, Dietrich</div></div><div class=""><div id=":1cw" class="" tabindex="0"><img class="" src="https://mail.google.com/mail/u/0/images/cleardot.gif" style=""></div></div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Jun 23, 2013 at 3:09 AM, Juan Jose Garcia-Ripoll <span dir="ltr"><<a href="mailto:juanjose.garciaripoll@gmail.com" target="_blank">juanjose.garciaripoll@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 class="gmail_extra"><div class="im"><br><div class="gmail_quote">On Sat, Jun 22, 2013 at 10:41 AM, Dietrich Bollmann <span dir="ltr"><<a href="mailto:dietrich@formgames.org" target="_blank">dietrich@formgames.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Do I misunderstand the meaning of :WIN32?</div><div>Is the build version still a 64 bit version and :WIN32 is added by error?</div>
<div>Is the variable ECL_WIN64 just ignored?</div>
<div></div></blockquote></div><br></div>This feature is related to the OS API that is used Win32 vs Mingw32 vs Cygwin32. On Windows64 the API used is still Win32, IIRC. I do not know how to change this without breaking some code out there, or whether the present situation is sensible or not. Maybe we coud at least push also Win64</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Juanjo<span class="HOEnZb"><font color="#888888"><br clear="all"><div><br></div>-- <br>Instituto de Física Fundamental, CSIC<br>c/ Serrano, 113b, Madrid 28006 (Spain) <br>
<a href="http://juanjose.garciaripoll.googlepages.com" target="_blank">http://juanjose.garciaripoll.googlepages.com</a>
</font></span></div></div>
</blockquote></div><br></div>