This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: mingw-hosted xgcc


> How I'm able to build a mingw-hosted H8/300 targetted cross egcs?

 Quite easily indeed ;-)

 1. Get a life, install Linux...

 2. Build a Linux-to-mingw32 (or Linux-to-cygwin-b20) cross-toolset.

 3. Build a Linux-to-h8300 cross-toolset (needed to build h8300-libs)

 4. Build a mingw32-to-h8300 cross-toolset using the 2. and 3. toolsets.
    (This is called the 'Canadian cross' -- Please see the Cross-GCC FAQ)

 Mumit Khan has pre-built mingw32 libs and DLLs, so the gdbtk-GUI is possible 
for mingw32 host too... Only problems seem to be the signal (error) handling
in GDB -- pushing a wrong button will exit the whole GUI... (just my first
experiences...)

 BTW, I was curious if the 'mingw32' idea could be used for generating Win32s
binaries, to use the 'crtdll.dll', 'w32skrnl.dll', 'w32scomb.dll' etc. coming
with the MS Win32s addition to Win3.1x... Seems to work quite well, only how
to get the 'native' compiler seems to be a big problem... My temporary solution
was to use DJGPP2.02 binaries. So the mingw32/win32s target compiler runs in
the DOS-Box. The prebuilt (with Borland 4.5) tcl/tk-DLLs work with Win32s, so
the tcltk-GUI was also possible for GDB... There are troubles with the 
missing 'console', linking tkConsole to GDB isn't ready yet -- all 'stdout' 
output goes to the GDB Command window... Ok, a 'mingw32-to-h8300-hms' GDB with 
GUI works just well (or badly) under Win3.1/Win32s as under NT/Win32... My own
tcl/tk-DLLs for Win32s (from 8.0pl2 sources, compiled with my new win32/win32s
cross-compiler under Linux), don't work (yet)...

 Cheers, Kai
_______________________________________________
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
_______________________________________________
To remove yourself from the crossgcc list, send
mail to crossgcc-request@cygnus.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.