Hi! I've been playing a bit with creating a mingw-w64 cross compiler, and used that to create a native mingw-w64 compiler. I haven't done /exactly/ what the doc says, but the cross compiler works (since it compiles the native compiler and the resulting binaries works) and the native compiler is working as far as I can see (it compiles hello.c without any problems and the resulting binary works.
But I've noted one thing. The directory mingw (which on linux is a symlink to x86_64-w64-mingw32) is just a copy of x86_64-w64-mingw32. And at least on my Windows machine, the mingw directory is really not needed. I moved it away and it still compiles working binaries. Is it because gcc is braindead that we really need that symlink? I can't quite understand why we need it in the first place. If you like I can document (to be put on the wiki) how I created my cross compiler. -- chs ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
