Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <4105AB1C.8060006@nycap.rr.com>
Date: Mon, 26 Jul 2004 21:08:44 -0400
From: Mathieu Malaterre <mmalater AT nycap DOT rr DOT com>
Reply-To: mathieu AT malaterre DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: INT32: jmorecfg.h
References: <4105A55B DOT 1010509 AT nycap DOT rr DOT com> <20040727005420 DOT GB8331 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20040727005420.GB8331@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Symantec AntiVirus Scan Engine
Note-from-DJ: This may be spam

Christopher Faylor wrote:
> On Mon, Jul 26, 2004 at 08:44:11PM -0400, Mathieu Malaterre wrote:
> 
>>Hi,
>>
>>	I am trying to compile VTK using the jpeg library shipped with 
>>	cygwin. And I have a problem of compilation:
>>	
>>Building object file vtkJPEGReader.o...
>>In file included from /usr/include/jpeglib.h:30,
>>                from /home/mathieu/Kitware/VTK/Utilities/vtk_jpeg.h:21,
>>                from /home/mathieu/Kitware/VTK/IO/vtkJPEGReader.cxx:23:
>>/usr/include/jmorecfg.h:250: error: conflicting types for `typedef long int
>>  INT32'
>>/usr/include/w32api/basetsd.h:52: error: previous declaration as 
>>`typedef int
>>  INT32'
>>
>>
>>	could someone patch the jpeg6b lib (look at line 249) :
> 
> 
> You're mixing cygwin includes with native windows includes.  That's not designed
> to work well.

VTK compiles / runs on:

- Nearly every Unix-based plateform (SGI, HP-UX, SUN ...)
- Windows 95/98/NT/2000/XP
- Tons of linux flavor
- Mac OS X
- *BSD

So I believe we have a rather clean approach. It's just the fact that 
defining INT32 globally without no namespace is rather dangerous, don't 
you think ? All I was asking, was just for a little barrier (since a 
barrier from XMD_H was already done).

my 2 cents
Mathieu

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/