Received: by cthulhu.engr.sgi.com (941129.SGI.8.6.9/911001.SGI)
	for tiff-list id IAA24189; Mon, 23 Jan 1995 08:31:27 -0800
Return-Path: <owner-tiff>
Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (941129.SGI.8.6.9/911001.SGI)
	for <tiff-relay@cthulhu.engr.sgi.com> id IAA24184; Mon, 23 Jan 1995 08:31:21 -0800
Received: from mcgltd.demon.co.uk by sgi.sgi.com via SMTP (941129.SGI.8.6.9/910110.SGI)
	for <tiff@sgi.com> id IAA04797; Mon, 23 Jan 1995 08:31:02 -0800
Date: Mon, 23 Jan 1995 16:18:29 GMT
From: Raymond@mcgltd.demon.co.uk (Raymond Wilson)
Reply-To: Raymond@mcgltd.demon.co.uk
Message-Id: <1120@mcgltd.demon.co.uk>
To: tiff@sgi.sgi.com
Subject: Compiling LIBTIFF for MSDOS...
X-Mailer: PCElm 1.10
Lines: 26
Sender: owner-tiff@sgi.sgi.com
Precedence: bulk

Hello,

I am trying to compile the LIBTIFF library (version 3.2) on an 
MSDOS machine using BCC 4.02. I have noticed that many parts of 
the LIBTIFF code use short meaning a TWO byte signed integer, 
whereas BCC 4.02 defines short as a signed ONE-byte integer (and 
seems disinclined to let me change it).

If anyone has already solved this problem (and there is a more 
elegant solution than ripping through the code changing short 
for int or likewise defined type) I'd love to hear it.

I have also noticed the correspondance on this list referring to 
v3.3 (still in beta form?). Perhaps this version has already 
corrected the 1-2 byte short problem.

Many thanks in advance for any help you can give.

Raymond.

-- 
Raymond Wilson,      Software Engineer.      Morgan Collis Group Ltd,
                                             The Mill, Millbrook Close,
Yes, they ARE fond of mills here!            St. James Mill Rd, 
Ph: +44 604 580-980  Fax: +44 604 589-208    Northampton NN5 5JF, Britain.


