LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
February 2010
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2010.02.18 15:59 "Re: OT: Visual C++ runtimes (was: Using libtiff in Visual C++ 6.0)", by Edward Lam2010.02.19 18:32 "Re: Using libtiff in Visual C++ 6.0", by Phillip Crews
On 2/18/2010 2:50 PM, Bob Friesenhahn wrote: > On Thu, 18 Feb 2010, Phillip Crews wrote: >> >> These issues are part of the reason to link statically whenever >> possible. It avoids an enormous number of build and especially run-time >> (customer) problems. >> >> Executables linked statically with later versions of MSCRT can run fine >> on earlier operating systems, though at some point compatibility with >> Windows 95/98/ME will probably break (and may already have; I don't >> support those O/Ses any more). > > It is wise to check the usage license for recent MSVC versions. The > usage license for recent versions seems to apply arbitrary > restrictions and limit what you are allowed to do and how you are > allowed to deploy your software. I seem to recall seeing restrictions > which would be bad for open source software. I am not sure how one > sees the usage licence after the software is already installed. Very true. The only egregious thing I've seen recently has been the "fluent user interface" part of MFC which I despise and don't use anyway. I haven't seen anything that makes it worse to link with different versions of the C runtime. For what it's worth, the old MSVCRT import libraries still come with Visual Studio (as of 2008), but I don't know what is required to use them. - Phillip