Interesting, I just had a discussion with Martin about this ... and I
completely agree, all those wrapped header files should be removed. Probably
we should also eventually make something similar to the configure mechanism for
mswin -- not necessarily an autoconf script, but at least something that asks
questions about how you want XEmacs compiled, and sets up the files
appropriately.
So I still think the Makefiles should go into the proper directories.
Adrian -- surely it can't be that difficult to rewrite your Lisp code.
ben
"William M. Perry" wrote:
Andy Piper <andy(a)xemacs.org> writes:
> At 08:46 PM 11/18/99 -0700, Ben Wing wrote:
> >I say, put all the nt makefiles in the proper directories, not in nt.
> >Windows is not a second-class citizen w.r.t. xemacs.
>
> I agree, but this is not strictly true - the windows build uses its own
> private versions of some header files and source files, noteably
> config.h, so it is defintely not the same as all other builds.
Most of the stuff in nt/inc is empty, and only needed because certain parts
of the code unconditionally include things like netdb.h instead of wrapping
them in #ifdef HAVE_NETDB_H, and doing the appropriate autoconf checks.
sys/param.h can be removed and the definition of NBPG put in nt/config.h
sys/ioctl.h, netinet/in.h, arpa/inet.h, netdb.h, unistd.h can be completely
nuked
sys/time.h is probably doing the wrong thing. We should just include the
correct file under windows instead of creating our own prototypes for
struct timeval, etc.
sys/socket.h should just be nuked and all the checks for net-specific
errnos should be wrapped in a new macro. In some of our code we use
ISSOCKETERROR(var,ENOTCONN), on windows this expands the WSA stuff for
you.
-Bill P.
--
ben
--
In order to save my hands, I am cutting back on my responses, especially to
XEmacs-related mail. You
_will_ get a response, but please be patient. If you need an immediate
response and itÂ’s not apparent in
your message, please say so. Thanks for your understanding.