Hi Ben!

On Tue, Feb 15, 2011 at 10:57 AM, Ben Key <[email protected]> wrote:
> Hello K. Frank,
>
> Thanks for your response.  I asked if Cygwin was required because it is not
> clear what I should download.  In the "Toolchains targetting Win32 /
> Automated Builds" area all of the builds that are not for the Mac or Linux
> have cygwin in the host field.  Can these builds be used without Cygwin or
> should I be downloading something else?

Hmm.  I hadn't paid attention to the naming of the automated builds.  (For
whatever reason, I've been using the personal builds.)  I would think that the
automated builds should run just fine on native windows (no cygwin; after all,
that's what they're for.  (This excludes, of course, the actual cross-compilers
that run, e.g., on linux, but produce windows executables.)

But the naming convention does raise the question.  Hopefully someone from
the mingw-w64 project might clear this up.  (Or you could also just download
it and try it out -- unless you have a slow connection or are short on disk
space, it's pretty painless.)

> There are builds in the "Toolchains targetting Win32 / Personal Builds" area
> that have mingw instead of cygwin in the host field but they do not seem to
> be kept as up to date as the "Toolchains targetting Win32 / Automated
> Builds" area.

I've been using personal builds, most recently:

   mingw-w64-bin_x86_64-mingw_20101002_4.5_sezero.zip

and it runs fine on (64-bit) windows 7 (no cygwin anywhere).

Note, I don't think that the automated builds are always the most up to date
(depending what you mean by that).  I believe I went with the above-mentioned
personal build because I wanted a gcc 4.5.1 compiler, and there was a
personal-build version at the time, but not an automated build.

> Thanks.

Good luck.


K. Frank

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to