<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><br><div><div>On May 22, 2013, at 10:16 PM, Charles Davis <<a href="mailto:cdavis5x@gmail.com">cdavis5x@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">, I'm well aware that there's quite a few Windows users on this list. Many of them don't have a shell that can run configure installed. For them, ditching autoconf in favor of CMake is a no-brainer. Why put so much effort into maintaining a build system a sizable proportion of our users can't even use?</div><br class="Apple-interchange-newline"></blockquote></div><br></div><div><br></div><div>Just a bit of info in case this isn't widely known and may be useful…<div><br></div><div>One can drive the MS compiler (cl.exe) and linker (link.exe) from Cygwin if he starts the cygwin shell from a Visual Studio command prompt which sets up the required environment variables. So, it is certainly feasible to use automate/autoconf on Windows if one chooses. The only irritation I ran into doing that was with path names. If memory serves me correctly, I had trouble passing absolute path names to things like the header search path switch. I had to use relative paths.</div><div><br></div><div>-James</div></div><div><br></div></body></html>