> > * do you foresee any issues with integrating with mingw.org's MSYS?
>
> There's no integrating to be done. All you have to do is download my
> full MSYS package here:
> http://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/MSYS%20%2832-bit%29/
>
> unzip it, run msys.bat and add the toolchain to PATH as in Linux.
Nice, great to see you've got the msys.bat that can use mintty. I'll check it
out but will likely end up scripting a recipe to download and assemble the
subset of MSYS pieces I use in addition to the other mingw artifacts (eg -
autoconf,automake,libtool) stuff I need. For 32bit, I think the key is to take
your 'mingw32' top-level dir and inject it as 'mingw' _under_ the typical MSYS
root dir so I don't have to futz with /etc/fstab or PATH. We'll see.
> > * do you have a {fossil,git,hg} repo for your build recipes source? As
> > I've not built toolchains, I'd like to learn by drafting off of your hard
> > work and, time permitting, play with creating a build script using
> > http://code.google.com/p/waf/
>
> Funny you should ask :)
> https://github.com/rubenvb/MinGW-w64-build-scripts
>
> There's five top-level scripts:
> buildmingw*.sh build native toolchains with the already compiler
> cross-toolchain (must have (x86_64|i686)-w64-mingw32-* tools in PATH)
> buildcross*.sh build linux x86_64 to mingw toolchains, do these first,
> be sure you have the development gmp/mpc/mpfr for your linux distro
> installed.
> versions.sh defines version numbers for all the packages, most
> important for everything but gdb and binutils. GCC_VERSION is used to
> name the zip files, all the rest are for finding the appropriate
> source directories.
>
> I suggest downloading the source package if you want to use the scripts.
>
> Mind you: the scripts are in a constant state of flux, mostly not
> working ;-) Checkout the "4.6.1-1" tag to get the ones distributed in
> the source package (which also contains the sources, and as I now have
> discovered a minor patched version of mpc-0.9 for shared libraries,
> these patches have already been sent upstream).
>
> A word of advice: MSYS for GCC building is
> slooooooooooooooo....ooooooow. I switched to a Virtualbox+Ubuntu and
> haven't regretted it yet. MSYS often gave weird errors about not being
> able to find files etc. while they were present. Don't recommend it at
> all (sorry to whoever wrote everything MSYS, but this is just my
> personal experience).
Thanks a ton for taking the time to describe things; I just need to take time
to woodshed on it. I'm hoping I can get things to reliably build on Win7 with
an installed MSYS/MinGW but I've always got my trusty VirtualBox+Arch system as
backup that, well, just rocks.
Jon
---
blog: http://jonforums.github.com/
twitter: @jonforums
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
