Kelly O'Hair wrote:
Maybe a PATH sanity check on the utilities used somehow, devise a simple use case for each utility used, and verify the utility from PATH is acceptable... Ah... but I know what you will say, just use autotools... well... does autotools work on Windows with VS2003? :^(
Last time around I had to use msvc 2003 from autotools, I used http://cccl.sourceforge.net/ to make it work, and it worked for me.
cheers, dalibor topic
