Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com To: "Robert Collins" Cc: , Subject: Re: updated win32 macro References: <035401c0ac91$3ba21fd0$0200a8c0 AT lifelesswks> <022001c0accf$29b724d0$0200a8c0 AT lifelesswks> <009901c0ad30$edf3d7b0$0200a8c0 AT lifelesswks> <00b101c0ad34$a1ad55d0$0200a8c0 AT lifelesswks> From: Akim Demaille Date: 15 Mar 2001 11:01:00 +0100 In-Reply-To: <00b101c0ad34$a1ad55d0$0200a8c0@lifelesswks> Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii | The developer could use | AC_PROG_CC_WIN32 | AC_CHECK_HEADER([windows.h]) | | and then (test in the configure script) / (surround the win32 code with | #IF_HAVE_WINDOWS_H), but I thought giving the developer a clear | mechanism would be nice. Then it seems to me that the interface is not right. Maybe something like AC_HEADER_WINDOWS which would do the whole thing might be what you need. Also, why do you set CC and not CFLAGS (and maybe LDFLAGS)? This is a tricky question, I often wondered, not only in the present case.