| 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.
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro edward
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro edward
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Lars J. Aas
- Re: updated win32 macro Lars J. Aas
- Re: updated win32 macro Robert Collins
