Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-l.b-one.net (mx-l.one.com [91.198.169.59])
	by mail9.b-one.net (Postfix) with ESMTP id BBDB940080A
	for <info@awaresystems.be>; Fri, 19 Feb 2010 19:54:33 +0100 (CET)
Received: by mx-l.b-one.net (Postfix, from userid 106)
	id AE09A72AF70; Fri, 19 Feb 2010 19:54:33 +0100 (CET)
X-Virus-Scanned: by one.com
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=0 required=4 tests=[none]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144]) by
 mx-l.b-one.net (Postfix) with ESMTP id CAC5A72AF69 for
 <info@awaresystems.be>; Fri, 19 Feb 2010 19:54:32 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by
 lists.maptools.org (Postfix) with ESMTP id DB1281D0E524C; Fri, 19 Feb 2010
 13:52:09 -0500 (EST)
Received: from cerious.com (mail.cerious.com [66.193.70.90]) by
 lists.maptools.org (Postfix) with ESMTP id DF5261D5BF04F for
 <tiff@lists.maptools.org>; Fri, 19 Feb 2010 13:32:05 -0500 (EST)
Received: from abaca.cerious.com (localhost.localdomain [127.0.0.1]) by
 abaca.cerious.com (Postfix-out) with ESMTP id 228323C409D for
 <tiff@lists.maptools.org>; Fri, 19 Feb 2010 13:32:07 -0500 (EST)
X-Propel-Return-Path: <pcrews@cerious.com>
Received: from cerious.com ([192.168.1.207]) by [127.0.0.1] ([127.0.0.1])
 (port 7027) (Abaca EPG outproxy filter 3.1.1.9369 $Rev: 9262 $) id
 7q1Yra2jiw70; Fri, 19 Feb 2010 13:32:07 -0500
Received: from cerious.com (unknown [192.168.1.102]) by abaca.cerious.com
 (Postfix-out) with ESMTP id 1947E3C409A for <tiff@lists.maptools.org>; Fri,
 19 Feb 2010 13:32:07 -0500 (EST)
X-Vipre-Scanned: 4D0B06000016364D0B074D-TDI
Received: from [192.168.1.113] (account pcrews HELO [192.168.1.113]) by
 cerious.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 13814815 for
 tiff@lists.maptools.org; Fri, 19 Feb 2010 13:32:03 -0500
Message-ID: <4B7ED924.6000306@cerious.com>
Date: Fri, 19 Feb 2010 13:32:04 -0500
From: Phillip Crews <pcrews@cerious.com>
Organization: Cerious Software Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7)
 Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: tiff@lists.maptools.org
References: <BAY128-W274F37D0CF5213A6E728EAF14A0@phx.gbl>
 <4B7AA6D8.7030806@3delight.com>	<BAY128-W2871B6605E984F07C5072AF1490@phx.gbl>
 <alpine.GSO.2.01.1002161107180.25017@freddy.simplesystems.org>
 <83C70DA01D8A4843AEFA5803F96EB4D4@KAM1720>
 <522c6461002161343v2042ab37l753fca7a860a7e00@mail.gmail.com>
 <4B7D562C.507@3delight.com> <4B7D7BCD.9010101@cerious.com>
 <alpine.GSO.2.01.1002181344110.25017@freddy.simplesystems.org>
In-Reply-To: <alpine.GSO.2.01.1002181344110.25017@freddy.simplesystems.org>
X-Propel-ID: 7q1Yra2jiw70
Subject: Re: [Tiff] Using libtiff in Visual C++ 6.0
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

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
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
