On 2013-06-01 00:06, Russ Allbery wrote: > Peter Rosin <p...@lysator.liu.se> writes: >> On 2013-05-31 19:19, Eric Blake wrote: > >>> That said, would it hurt if autoconf just unconditionally defined the >>> macros that were previously conditionally defined by a probe, so that >>> code that was relying on HAVE_STRINGS_H instead of blind inclusion will >>> still compile? > >> How would one do to be portable to both "some versions of FreeBSD" and >> MSVC, then? (MSVC 10 also lacks strings.h, btw) One camp needs >> HAVE_STRINGS_H to be defined and one needs to not have it defined. >> Sounds evil to unconditionally define it under those circumstances. Or >> have I misunderstood something? > > Autoconf doesn't work with MSVC directly so far as I know. All of the > packages I have that are ported to MSVC have a separate hand-written > config.h that's used for MSVC builds, and in that file one simply doesn't > define HAVE_STRINGS_H.
What do you mean directly? MSYS can drive a build using MSVC as toolchain (instead of MinGW) just fine. I do it all the time. Cheers, Peter
