Hello!
Is there any reason to keep DOS and OS/2 support?
I understand that I can find FreeDOS and try using it, but this
doesn't seem practical. As for OS/2 I'm not aware of any upstream
support at all, I think it is simply missing.
I propose to remove support for DOS and OS/2.
Regardless of this proposal I suggest following changes to Makefile.in,
which bring usage of more common idioms:
--- Makefile.in.orig 2008-12-14 03:24:05.000000000 +0300
+++ Makefile.in 2008-12-14 17:25:35.000000000 +0300
@@ -1012,14 +997,18 @@
./config.status --recheck
#create files for DOS, because DOS cannot do it itself
-makefile.dos engine/makefile.dos: mkdosmf.sed Makefile.in engine/Makefile.in
+makefile.dos: mkdosmf.sed Makefile.in
sed -f mkdosmf.sed <Makefile.in >makefile.dos
+
+engine/makefile.dos: mkdosmf.sed engine/Makefile.in
sed -f mkdosmf.sed <engine/Makefile.in >engine/makefile.dos
-makefile.os2 engine/makefile.os2: mkos2mf.sed Makefile.in engine/Makefile.in
+makefile.os2: mkos2mf.sed Makefile.in
sed -f mkos2mf.sed <Makefile.in >makefile.os2
- sed -f mkos2mf.sed <engine/Makefile.in >engine/makefile.os2
echo '%.o: %.c' >>makefile.os2
echo ' $$(GCC) $$(CFLAGS) $$(CPPFLAGS) -c $$<' >>makefile.os2
+
+engine/makefile.os2: mkos2mf.sed engine/Makefile.in
+ sed -f mkos2mf.sed <engine/Makefile.in >engine/makefile.os2
echo '%.o: %.c' >>engine/makefile.os2
echo ' $$(GCC) $$(CFLAGS) $$(CPPFLAGS) -c $$<'
>>engine/makefile.os2
--
HE CE3OH...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
