Mail Archives: djgpp/2018/04/14/07:00:06
In article <CAA2C=vC0Bydw2gijQMKaUcKyaWGZXFgdB
+vvN5GQR5MrQtEQzw AT mail DOT gmail DOT com>, djgpp AT delorie DOT com says...
>On 4/10/18, rugxulo AT gmail DOT com [via djgpp AT delorie DOT com] <djgpp AT delorie DOT com>
wrote:
>> Hi,
>>
>> On Friday, April 6, 2018 at 4:10:41 AM UTC-5, neozeed wrote:
>>>
>>> If the NTVDM can't nest properly, isn't it easier to just use
>>> a Win32 native version of GCC, and keep your CC1/CPP/GAS/LD native?
>>
>> (I think I misunderstood this comment the first few times that I read
it.)
>>
>> So you're saying use a Win32 (PE/COFF) gcc.exe as frontend with other
>> .EXEs remaining DJGPP (DOS, MZ/COFF)?
>
>I think he means a canadian-cross. i.e. run natively on win32 or
>win64 with all tools being win32/or win64 exes, and target djgpp.
>E.g.: https://github.com/andrewwutw/build-djgpp.git
For my own use, I wanted to get gcc 2.7.2.1 & binutils 2.8.1 running as a
cross to build ancient MAME / Allegro, I had some issues doing a standard
cross compile setup, but I dwas able to find the source fragment setup, and
re-build them first under DOSBox, then go back on the makefile, and use
MinGW to re-build the source behind the 'native' build, giving me a tool
chain that was able to deal with Allegro's specific macros & asm, and being
able to compile things like doom in under 2 seconds...
For the purist I'd just make the only things that are really needed to be
native, native, in this case gcc.exe and possible cpp.exe to handle the long
file names. You can use the MS-DOS Player, to not only run MS-DOS / DJGPP
exe's under Win64, this way, but MS-DOS Player can wrap them so that they
can be simply invoked like any other exe. On 32bit machines, CC1/GAS/LD
ought to work as they did before, allowing these componets to remain
'native', or via something like MS-DOS PLayer.
http://takeda-toshiya.my.coocan.jp/msdos/
I guess my larger point is that all hope is not necessarily lost.
- Raw text -