Re: [Mingw-users] Mingw32 for Linux?? Now I Understand...!

[Kai R. <kai...@lu...>]

> Tom Williams wrote:
> 
> I think binutils and gcc can be hosted on ANY system (Unix or otherwise)
> and still target Mingw32.......

 Probably so... I still have DOS/DJGPP2-hosted toolsets for producing Win32 and
Win32s binaries under DOS. The 8+3 filenames forced me to use an 'emx-like' linker
and leave the 'lib' away from the library names (the emx lib names don't use the
'lib' prefix either):

 Directory of G:\usr\local\mingw32\lib

[.]          [..]         tapi32.a     tcl80.a      th32.a       thunk32.a
tix4180.a    tk80.a       url.a        user32.a     uuid.a       vdmdbg.a
version.a    vfw32.a      win32spl.a   wininet.a    winmm.a      winspool.a
winstrm.a    wow32.a      wsock32.a    wst.a        CRT_nogl.o   crt1.o
[ldscript]   crt2.o       dllcrt1.o    dllcrt2.o    [win32s]     advapi32.a
c.a          cap.a        comctl32.a   comdlg32.a   crtdll.a     ctl3d32.a
d3dim.a      d3drm.a      d3dxof.a     ddraw.a      dinput.a     dlcapi.a
dplayx.a     dsetup.a     dsound.a     dxguid.a     gdi32.a      glaux.a
glu32.a      glut.a       glut32.a     gui.a        imm32.a      itcl.a
itcl30.a     itk.a        itk30.a      kernel32.a   lz32.a       m.a
mapi32.a     mfcuia32.a   mgmtapi.a    mingw32.a    moldname.a   monamevc.a
mpr.a        msacm32.a    msvcrt.a     msvcrt20.a   msvcrt40.a   nddeapi.a
netapi32.a   odbc32.a     ole32.a      oleaut32.a   olecli32.a   oledlg.a
olepro32.a   olesvr32.a   opengl32.a   penwin32.a   pkpd32.a     rasapi32.a
rpcdce4.a    rpcns4.a     rpcrt4.a     scrnsave.a   scrnsavw.a   shell32.a
svrapi.a

 Also the install-dir names are shorter and with only one dot in them:

G:\usr\local\bin>gccmgw -v
Reading specs from /usr/local/lib/gcc-lib/mingw32/2_95.2/specs
gcc version 2.95.2 19991024 (release)

G:\usr\local\bin>gccmgw-e -v
Reading specs from /usr/local/lib/gcc-lib/mingw32/egcs-1.12/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)

 I have always wondered if using the name 'Mingw' is allowed for a toolset
which can produce executables for all the 'Win32*' variations... Should the
'Maxgw' be used ? ("Maxgw gives the maximum for the Win32* target choices" ;-)

 Ok, the three-phase linking needed for the Win32s executables is a little tough,
but putting it into a Makefile isn't so hard... After the template for the link
commands is ready, it isn't a problem any more... Or one could make a '.BAT' for
the 'linker'...

 The 'DOS-hosted-Win32*-targeted Mingw'-toolset is only a toy. Although I have
built Insight's etc. for Win32s, I have built them under Linux... And only some
simple Win32s apps under DOS. Of course also the DJGPP2-hosted tools were produced
under Linux with a Linux-x-DJGPP2 toolset...

 DOS as the development environment isn't very good after all... (Some could say
the same about Win9x/NT too...). Ok, has anybody built a OS/2-emx hosted and Mingw-
targeted toolset ?  (Perhaps I built one some time but don't remember doing it...)
Perhaps the Mingw-x-emx toolset is more common, to produce Warp-binaries under
Windoze...

Cheers, Kai