|
| From: | Paul Eggert |
| Subject: | Re: [RFC] Correctly handling MinGW-w64 |
| Date: | Mon, 17 Nov 2014 07:18:45 -0800 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 |
Óscar Fuentes wrote:
I thought that this type of tasks are the raison d'être of `configure'.
No, the point of 'configure' is to do things that ordinary C and 'make' cannot. Here, we have something that ordinary C can do, so 'configure' isn't needed.
Doing that is a kludge.
Perhaps, but doing it in 'configure' is a worse kludge. The stuff in 'conf_post.h' is, by design, included everywhere, and it's the logical place to put global things that don't need 'configure''s help.
More generally, it would be better yet if we didn't need a global symbol indicating which particular minor flavor of a Microsoft Windows development environment is being used. Symbols like that are needed in src/w32*.c but it'd be nicer if they didn't need to be used in generic code.
| [Prev in Thread] | Current Thread | [Next in Thread] |