Return-Path: <tiff-bounces@remotesensing.org>
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx015.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j538K1Xk003001
        for <joris.at.lebbeke@skynet.be>; Fri, 3 Jun 2005 10:20:02 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id B864A25D63BD; Fri,  3 Jun 2005 04:19:40 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207])
	by xserve.flids.com (Postfix) with ESMTP id 3118625D6398
	for <tiff@remotesensing.org>; Fri,  3 Jun 2005 04:19:39 -0400 (EDT)
Received: by wproxy.gmail.com with SMTP id 68so796064wri
	for <tiff@remotesensing.org>; Fri, 03 Jun 2005 01:19:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=jDZla4Kgo6nQJopFeb8hYXuEmeoBQfBL9OMV5PnU8Ks+hcNudaTHZhsfbMB8C48Wwa570ILrRpKYjXaUWSzdmsTGGgmyrOYAgSY6UBs2s6OwY+rjboU3d1v2ufxoxHoCmPvqMJiMvOoT3hoxEmdkKgH9I4SOpaEwi+sqd/2Z9Lk=
Received: by 10.54.80.7 with SMTP id d7mr986625wrb;
	Fri, 03 Jun 2005 01:18:52 -0700 (PDT)
Received: by 10.54.100.7 with HTTP; Fri, 3 Jun 2005 01:18:52 -0700 (PDT)
Message-ID: <92d3a4950506030118e473fec@mail.gmail.com>
Date: Fri, 3 Jun 2005 10:18:52 +0200
From: Antoine <melser.anton@gmail.com>
To: Edward Lam <edward@sidefx.com>, tiff@remotesensing.org
Subject: Re: [Tiff] vb port soon available
In-Reply-To: <429F7366.6020308@sidefx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <92d3a49505060213505cc3aea7@mail.gmail.com>
	<429F7366.6020308@sidefx.com>
Cc: 
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Antoine <melser.anton@gmail.com>
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by inmx015.isp.belgacom.be id j538K1Xk003001
X-UIDL: 000000000023ceae.0000032a
X-MSP-STORE: Fri, 03 Jun 2005 10:20:07 +0200
Status:   

On 6/2/05, Edward Lam <edward@sidefx.com> wrote:
> I think that a better approach would have been to add something like TIFF_EXPORT
> in front of all the functions that we need to export. And then we can just have
> some options to control this #define in config.h.
> 
> On Windows for example, one can use this to do away with the need for a .def
> file by doing:
> 
> #define TIFF_EXPORT __declspec(dllexport)
> 
> This would allow everything to go into one baseline. I detect multiple baselines
> because what happens if a bug gets fixed in only 1 of them?

This would clearly be better, but I assumed that as it hadn't already
been done then there was a reason why not. Maybe not. I would think
that we should keep the .def file (seems nicer to keep the exports in
one place), but maybe have a flag on the compile line that if
provided, would define __stdcall for the appropriate functions. If you
think this would be ok then I could have a go at it. I can take some
inspiration from what is there.
I clearly thought that there was no interest in VB (and had no idea
why it didn't "just work"), if the contributors are OK to start having
a bit more doze specific stuff in conditional defines then great, I'd
be over the moon for it to go into the std distro... that means I
don't have to redo it for every release! If not, then I'll keep
plugging along and get the sourceforge site up and running. I am also
going to be working on an activex that will encapsulate some libtiff
functionality, but will also use freeimage (freeimage doesn't give you
much freedom with your tiff options) - that is probably not so good
for contrib.
Cheers
Antoine
-- 
G System, The Evolving GUniverse - http://www.g-system.at
_______________________________________________
Tiff mailing list: Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/

