Going back to the original post:
uncharted wrote:
Start off as simply a bunch of replacement files that goes on top of an OS3.1 install and keep building them up until you have replaced everything. ... Really, it's how AROS should have been done from the start.
I don't follow AROS that closely, but you mean this is not being done for the non-hardware banging code?! GCC should be able to produce both 68K and x86 files; load the 68K on a hardware Amiga in place of the regular library or whatever, test the heck out of it, and if it passes try the other version in AROS.Isn't this rather standard procedure for trying to develop identical functionality on two different platforms?
