I'm trying to understand which download archive I should be using and/or possibly ask for an additional "Release for …" archive.
Ultimate goal is to build Win64 DLLs using a Win64 version of MinGW-w64.
Sezero provided pointed me to one of his personal archives, however, this is for eventual use as a captive compiler in a product and therefore feel it should be coming out of a an officially tagged "Release for …" folder vs an automated or personal folder.
Sezero's mingw-w64-bin_x86_64-mingw_20100123_sezero.zip build worked just fine for my actual needs.
Also tried mingw-w64-1.0-bin_i686-mingw_20100129.zip and it too works, although, I have to use the toolchain prefixed gcc name (and objdump -fa comfirmed it was 64b).
What looks like the closest "Release for …" archive is mingw-w64-bin_i686-cygwin-1.5.25-15_4.4.1a.tar.bz2, but I'm not sure if this is quite the same thing, but as soon as I try to run x86_64-w64-mingw32-gcc-4.4.1-1a.exe, I get … popup with application was unable o start correctly (0xc000000d). Click OK to close application.
Based on name being *i686-cygwin* vs *i686-mingw32*, I suspect I need cygwin loaded somewhere and something set or possibly me running W7 64b might also have something to do with it.
So I need some direction, is mingw-w64-bin_i686-cygwin-1.5.25-15_4.4.1a.tar.bz2 what I should be looking for in the first place (because I can't confirm what it produces) and why doesn't it run … is it a set up issue of second package?
If this isn't the equivalent of mingw-w64-1.0-bin_i686-mingw_20100129.zip, why isn't there one in the "Release for …" folder (and who do I ask to get one)?
If it is a question of loading and setting up multiple packages, I suppose I could deal with it once I know the particulars, but ideally, I'd prefer single package, download, install, use.
The naming of our toolchains is the following: <target>-<host>-<date-of-build>
<target> is "mingw-w32" for 32-bit Windows targeting toolchains, or "mingw-w64" for 64-bit Windows targeting toolchains.
<host> is the triplet describing the host environment you are using to build. Eg. i686-mingw32 is 32-bit native Windows host. i686-linux is linux 32-bit i?86 host version of the toolchain. x86_64-linux is the linux 64-bit amd64 host version of the toolchain.
The toolchains for building (targeting) x64 Windows are to be found in "Toolchains targetting Win64 " on download page.
Not sure we are totally talking about the same thing, let me re-ask …
I get that I should be using a mingw-w64 archive, but what is i686-cygwin vs i686-mingw archives (which may explain why i686-cygwin does not even execute for me or I'm missing something) and why is there no i686-mingw in the "Release for …" folder (or is the purpose of that folder to be some release check point (ie production vs test builds).
Usual file name pattern is:
mingw : well, that is what we are..
: this packgage will gnerate binaries for this
: Is the package a binary or a source packgage
: Which type of Host/OS this binary package will run
: a vers.number, date, and/or some other indicator
Examples on hypothetical package names:
This package runs on i686-cygwin (v1.5.25-15 at least) and targets
w64, it is built from sources dated 20100123. This is actually
a windows package, but if you don't have cygwin installed on your
windows, you can't run this. (see http://cygwin.com/ for what
This package runs on i686-mingw (which is i686-windows
ie. win32) and targets w64, it is built from sources dated
20100129. This, you can run natively on both win32 and win64,
and target win64.
This package runs on x86_64-mingw (which is x64-windows
ie. win64/amd64) and targets w64, it is built from sources
dated 20100129. This, you can run natively on win64-only
and target win64.
I hope this at least covers the file name stuff.
Ok, that clears up which does what and why cygwin version was throwing an error for me (and therefore I would not want to use it for my end purpose as it involves more set up).
So that leaves me with … why is there no i686-mingw in the "Release for …" folder (if folder purpose is release check point (ie production vs test builds) or is that not the point of the folder?
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.