> -----Original Message-----
> From: mingw-users-admin@...
> [mailto:mingw-users-admin@... Behalf Of Erik de
> Castro Lopo
> > Hello.
> > I tried to scrounge the 'net for info on using Mingw to cross compile to
> > another target, but I only found howtos to compile to Mingw from Linux.
> > Is it possible to use Mingw on Windows to compile to another
> target machine
> > (specifically MC68000 in this case)?
> You would probably be better off using the Cygwin tools for this, because
> they give you a much more complete environment and this kind of thing
> is more commonly done with those tool.
Actually building a cross compiler with mingw isn't as difficult as some
people seem to think. I've taken the liberty of adding a page to the MinGW
Wiki on this very subject. The page can be found at
hope I've covered the process quite well, if the rest of the list would care
to check it over in case I missed anything.
The resulting toolchain is quite a lot faster than the cygwin equivalent -
that really has to be seen to be believed and, even then, it's still quite a
In order to build gcc under MinGW/MinSYS I had to add 2 additional patches
to the sources available on the MinGW site. Should I add these patches to
the page or should they be added to the prepatched sources and/or diffs?
--- x-mingw32.orig Sat May 15 18:33:41 2004
+++ x-mingw32 Tue May 11 13:17:28 2004
@@ -2,6 +2,7 @@
# Make local_includedir relative to EXEC_PREFIX
local_includedir=$(libsubdir)/$(unlibsubdir)/..`echo $(exec_prefix) |
sed -e 's|^$(prefix)||' -e 's|/[^/]*|/..|g'`/include
# host runtime lib's printf uses 'I64' format specifier prefix instead
# of 'll' for HOST_WIDEST_INT_PRINT_*. See hwint.h.
--- mklibgcc.in.orig Sat May 15 18:33:35 2004
+++ mklibgcc.in Tue May 11 12:54:15 2004
@@ -39,6 +39,7 @@
echo 'srcdir = @srcdir@'
echo 'VPATH = @srcdir@'
echo 'EQ = ='
+echo 'INCLUDES += -I@...@'