Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas010.isp.belgacom.be (localhost [127.0.0.1])
        by inav014.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id j85ADn4g030407
        for <joris.at.lebbeke@skynet.be>; Mon, 5 Sep 2005 12:13:50 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx014.isp.belgacom.be (inmx014.isp.belgacom.be [195.238.2.217])
        by inas010.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id j85ADhdG011547
        for <joris.at.lebbeke@skynet.be>; Mon, 5 Sep 2005 12:13:43 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx014.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j85ADaxD018441
        for <joris.at.lebbeke@skynet.be>; Mon, 5 Sep 2005 12:13:36 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id j85A5mLa012165;
	Mon, 5 Sep 2005 06:06:34 -0400
Received: from web60223.mail.yahoo.com (web60223.mail.yahoo.com
	[209.73.178.111])
	by duke.maptools.org (8.12.11/8.12.10) with SMTP id j85A5iQS012135
	for <tiff@lists.maptools.org>; Mon, 5 Sep 2005 06:05:44 -0400
Received: (qmail 58794 invoked by uid 60001); 5 Sep 2005 10:05:44 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=LGG3bRpI21tyqfhyhWa+5GxvUjgvRo/2q3XHe0GwAxr3NMNPYUs/Z4Ix+7aUfTMYrqoBgCqj1UkuCKRGpX68CkQXwLrNGM0FdALFJfFPrte5AmENinh18IInf5ps1JgnbRfMC8HVXbP+pDEjYHg9OVoQ2BtbD20ReEePvryfyKU=
	; 
Message-ID: <20050905100544.58792.qmail@web60223.mail.yahoo.com>
Received: from [192.146.101.26] by web60223.mail.yahoo.com via HTTP;
	Mon, 05 Sep 2005 03:05:44 PDT
Date: Mon, 5 Sep 2005 03:05:44 -0700 (PDT)
From: katrina maramba <ka3na_423@yahoo.com>
Subject: Re: [Tiff] Porting libtiff to ARM
To: Rob van den Tillaart <rvdt@oce.nl>
In-Reply-To: <431BED17.D88B8DC3@oce.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Cc: tiff@lists.maptools.org
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
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>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00000b90
X-MSP-STORE: Mon, 05 Sep 2005 12:13:50 +0200
Status:   

Thanks for the hint Rob. :)  If anyone's got a more
detailed documentation/notes on porting, Id appreciate
it if I can get a copy.

Also, does anyone know of the specific API that takes
care of the strip chopping?  So maybe I can take a
closer look at it.  I found
ChopUpSingleUncompressedStrip(). I tried breaking in
the API, but it seems that it doesn't go there...

I am so lost right now.  You see, the big problem is
lack of memory.  So the strip chopping process should
be available coz this helps out a lot.  If anyone also
has good memory management for libtiff, maybe you
could share it to the group.. :)

Thanks a lot,
Kat



--- Rob van den Tillaart <rvdt@oce.nl> wrote:

> 
> Hi Katrina,
> 
> A recent hint in the libtiff archive:  
> http://www.asmail.be/msg0055178667.html
> 
> As I have no experience with ARM processor you might
> look for a linux
> distribution for ARM containing libtiff? COuld
> contain some compile
> hints.
> 
> regards,
> rob
> 
> 
> katrina maramba wrote:
> > 
> > Hello,
> > 
> > Do you have any notes/ documentation on how to
> port
> > libtiff to ARM? I am having problems porting.
> > 
> > Also, I noticed something... I had modified the
> > makefile and I didn't join tif_win32.c and
> > tif_stream.cxx in the build since they had some
> > compile and link errors so I thought I'd give it a
> try
> > without these two files.  In doing so, the parser
> > still ran but the strip chopping process is no
> longer
> > done (I did a comparison with my workspace that
> had
> > all the files).  Is it correct to assume that the
> > strip chopping process is not done because of the
> > "deletion" of the two files from the makefile?
> > 
> > Thanks,
> > Kat
> > 
> > 
> > 
> >
>
______________________________________________________
> > Click here to donate to the Hurricane Katrina
> relief effort.
> > http://store.yahoo.com/redcross-donate3/
> > _______________________________________________
> > Tiff mailing list: Tiff@lists.maptools.org
> > http://lists.maptools.org/mailman/listinfo/tiff
> > http://www.remotesensing.org/libtiff/
> 
> 



	
		
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
