[Gdal-dev] 12 bit Jp2k image questions.
Collins, Benjamin
collinsb at mitre.org
Fri Dec 8 09:12:24 EST 2006
>-----Original Message-----
>From: gdal-dev-bounces at lists.maptools.org
>[mailto:gdal-dev-bounces at lists.maptools.org] On Behalf Of
>Frank Warmerdam
>Sent: Thursday, December 07, 2006 1:16 PM
>To: Daniele Romagnoli
>Cc: gdal-dev at lists.maptools.org
>Subject: Re: [Gdal-dev] 12 bit Jp2k image questions.
>
>Daniele Romagnoli wrote:
>> Hi,
>> out of curiosity, I'm trying to build GDAL with Kakadu
>support for JP2K.
>>
>> I have downloaded the Kakadu windows library but when I
>build GDAL this
>> error occurs:
>>
>>
>---------------------------------------------------------------
>-----------------------------------------------------------
>>
>> D:\gdal\frmts>cd jp2kak && nmake /NOLOGO /f makefile.vc
>> <http://makefile.vc> && cd ..
>> cl /nologo /MD /EHsc /Zi /Fd..\..\gdal.pdb -I..\..\port
>> -I..\..\ogr -I..
>> \..\gcore -I..\..\alg -ID:\WORK\kakadu /DKDU_PENTIUM_MSVC /GX /c
>> jp2kakdataset.
>> cpp
>> jp2kakdataset.cpp
>> jp2kakdataset.cpp(119) : fatal error C1083: Cannot open
>include file:
>> 'jp2_local
>> .h': Invalid argument
>> NMAKE : fatal error U1077: 'cl' : return code '0x2'
>> Stop.
>>
>---------------------------------------------------------------
>-----------------------------------------------------------
>>
>>
>> Where can I find jp2_local.h in order to build GDAL?
>
>Daniele,
>
>It is within the Kakadu source tree. The problem with windows builds
>that include Kakadu is that when I build Kakadu on windows, I actually
>extract all the files I need out into a single directory and build
them
>with my own scripts rather than use the normal Kakadu build mechanism.
>This lets me assemble the various files I need, including a bunch from
>the kakadu apps subtree. The downside it is essentially a process of
>experimentation for other developers to figure out how this
>can be done.
>
Daniele,
If you have the source (on Windows) it's enough to build all of Kakadu,
then do a windows 'search' and copy all the *.h and *.obj files to one
directory. Then list that directory as KAKDIR in the nmake.opt. This
is not scripted, but since I just compiled Kakadu once, it's just a
onetime process.
--
Ben
More information about the Gdal-dev
mailing list