[NSIS-Bugs] [ nsis-Bugs-2949102 ] nsis and mingw-w64 cross compile

[SourceForge.net <no...@so...>]

Bugs item #2949102, was opened at 2010-02-10 16:16
Message generated for change (Comment added) made by alonbl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=2949102&group_id=22049

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build System
Group: 2.0 Series
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Alon Bar-Lev (alonbl)
Assigned to: Amir Szekely (kichik)
Summary: nsis and mingw-w64 cross compile

Initial Comment:
Hello,

I am trying to build nsis with mingw-w64 project [1].

This project is better maintained and much more complete in many ways.

Some difficulties...

1. New triplets should be added:
i[3-6]86-w64-mingw32
x86_64-w64-mingw32

2. min() is not defined.

3. Includes should be at lower case.

4. Library gets:
/usr/lib/gcc/i686-w64-mingw32/4.4.2/../../../../i686-w64-mingw32/sys-include/commctrl.h:14:2: error: #error _WIN32_IE setting conflicts

5. bug#1753070 at the end I cannot link and run 32bit on my machine... So I cannot test the above.

Attached is a patch I created for 1-4.


[1] http://mingw-w64.sourceforge.net/

----------------------------------------------------------------------

>Comment By: Alon Bar-Lev (alonbl)
Date: 2010-02-20 19:04

Message:
The problem is not that the header defines its own value, but the header
does not compatible with older interface.

I prefer autotools build system, and not fully understand nsis... But you
can probably define this to different values if compiling using MSC or
MinGW, right?

Or in source:

#ifdef _MSC_VER
#define _WIN32_IE <whatever>
#else
#define _WIN32_IE <whatever>
#endif

What do you prefer?

----------------------------------------------------------------------

Comment By: Amir Szekely (kichik)
Date: 2010-02-20 18:31

Message:
Thanks for the patch. I'm a bit afraid of the _WIN32_IE change. The
resulting installer should work on Windows 95 and above. That kind of
change might make that impossible. I am fully aware of all that stands
behind and against this, but an obscure compiler compatibility is not a
reason to drop it. Besides, it looks more of a bug in the headers as
_WIN32_IE is supposed to modify their behavior. The header should not
define it on its own.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=2949102&group_id=22049