Hi!
4-Авг-2006 07:12 [EMAIL PROTECTED] (Blair Campbell) wrote to
freedos-user@lists.sourceforge.net:
>> I think, build subsystem _should_ be _added_ before "final" EMM386
>> version will be released - else, because "no more permanent, than
>> temporary", EMM386 may never get build subsystem, which allows to 3rdp party
>> developers to properly check their patches before submitting.
BC> I don't think it's too hard for a developer to add his makefile
BC> himself.
Yes, he may. But, for example, with different option set resulting
executable may work differently (if work at all). The more so, I don't know,
how Michael packs executables, so I can't reproduce _identical_ binary. The
more so, currently EMM386 sources are _not_ compilable by TC/BC at all -
because warnings and because different case names (see my patch, which
fixes this). I suggest, with TCPP same trouble, so, probably, Michael uses
some subtle trick to workaround this in his makefiles.
BC> Lots of the FreeDOS source packages come without makefiles
BC> or batch files.
This is another story. And, of course, this is very bad. :(
PS: BTW, do you remember, that FreeCOM also isn't compilable by TC/BC (no
or different prototypes; unsupported comments style; using non-defined
variable fddebug; extra warnings like assignment const pointer to non-const;
missing "#include <stdarg.h>"; using "#pragma -a" instead "#pragma option
-a" and using "#pragma option" at all; using explicit "_seg"; etc)? I still
wait, when you apply my fixes for this.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
