[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] Correctly handling MinGW-w64

From: Eli Zaretskii
Subject: Re: [RFC] Correctly handling MinGW-w64
Date: Mon, 17 Nov 2014 17:55:50 +0200

> From: Óscar Fuentes <address@hidden>
> Date: Mon, 17 Nov 2014 15:59:47 +0100
> Paul Eggert <address@hidden> writes:
> > Óscar Fuentes wrote:
> >>> into ms-w32.h or into some other header specific to Microsoft Windows?
> >> We don't have a header that is included by all the .c files, right?
> >
> > Every .c file includes stdbool.h, string.h, and stdlib.h, via
> > conf_post.h.  If none of those serve, you can include whatever file
> > you like (stdio.h, say), in ms-w32.h or something like that.
> Doing that is a kludge. At some point on the future someone will change
> how some of those files are #included (or remove them altogether).

Whatever happens, ms-w32.h will always be included in conf_post.h.

> I thought that this type of tasks are the raison d'être of `configure'.

So did I.  I'm confused and perplexed to hear arguments to the
contrary.  Didn't we toss the src/s/*.h files for this very reason?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]