NSIS uses wrong MinGW cross toolchain

Windows installer development tool

Brought to you by: anders_k, eccles, joostverburg, justin1014, and 2 others

#1032 NSIS uses wrong MinGW cross toolchain

Milestone: 2.0 Series

Status: open

Owner: nobody

Labels: Build System (70)

Priority: 5

Updated: 2011-05-20

Created: 2011-05-20

Creator: Volker Diels-Grabsch

Private: No

On a system where multiple MinGW cross toolchains are installed (e.g. one by the distro and one self-compiled), NSIS might pick the wrong one.

The attached patch solves this issue by providing a way to specify the toolchain prefix to use (MINGW_CROSS_PREFIX).

See also: http://lists.nongnu.org/archive/html/mingw-cross-env-list/2011-05/msg00021.html

Discussion

Volker Diels-Grabsch - 2011-05-20

allow to specify the mingw cross toolchain via MINGW_CROSS_PREFIX

nsis-1-explicit-mingw-cross-prefix.patch

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Volker Diels-Grabsch - 2011-05-20

labels: --> Build System

milestone: --> 2.0 Series
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

f0rt - 2011-06-25

A fix for the reported bug was committed into the subversion repository (revision 6156).

The command line option XGCC_W32_PREFIX could be used to explicitly select a specific win32 targeted cross compiler. The value of XGCC_W32_PREFIX has to be the prefix of the toolchain. For example XGCC_W32_PREFIX=i686-w64-mingw32 would deploy the win32 targeted MinGW-w64 cross compiler if it is available on the build system.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.