MSVC 2008 is certainly a problematic requirement for many people. As we have discussed before, one idea, which I still believe we should implement, is to get rid of all MS compiler dependencies. This means that the Autotools toolchain, GCC, and NASM could be used an all platforms.I agree with getting rid of MS compiler dependencies and using MSYS or Cygwin. But I don't think MSVC 2008 is as problematic as you think. The compiler is available for free these days, and it's easier for most people to install than a full-blown Cygwin distribution.
The MSVC compiler might be free today, but what about tomorrow? The history also indicates that MS moves quite rapidly when it comes to development environments: The 2008 version might soon be replaced with something new and incompatible. This has happened numerous times before. In fact, when I started working with TightVNC, one problem I had was that the build system required MSVC 6.0, but that version wasn't available any longer...
MSVC also has some other serious limitations, such that it only supports compiling code that's are located on local drives. Samba shares, for example, does not work. (At least this was the case last time i checked.)
If you use MSYS, Cygwin is not necessary. So I think it's safe to say installing MSYS, MinGW and even NASM on Windows should be as easy or even more easy than installing MSVC 2008.
Best regards, ---
Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
