[Gdal-dev] ECW Source SDK Available - Linux Binaries Prepared

[Steve Halasz]

On Thu, 2005-01-27 at 14:09 -0500, Steve Halasz wrote:
> On Wed, 2005-01-26 at 01:07 -0500, Frank Warmerdam wrote:
> > Folks,
> > 
> > The long awaited release of the ECW SDK from ERMapper has finally arrived,
> > and I have built the code for Linux (with gcc 3.3).  The building is a bit
> > tricky, so I thought it might be of interest to some folks to have pre-build
> > binaries for linux.  I have put them at:
> > 
> >    http://gdal.org/dl/ecwsdk-3.1.25Jan05-linux.tar.gz
> > 
> > I *think* this should work with gdal 1.2.5.
> 
> Trying to compile with 1.2.5 I get:
> 
> make[3]: Entering directory
> `/home/steve/projects/qgis/debian/gdal/gdal-1.2.5/frmts/ecw'
> ../../GDALmake.opt:281: *** Recursive variable `CPPFLAGS' references
> itself (eventually).  Stop.
> 
> My GDALmake.opt has:
> 
> CPPFLAGS        =  -I$(GDAL_ROOT)/port
> -I/home/steve/downloads/ecwsdk-3.1.25Jan05-linux/include
> 
> And frmts/ecw/GNUmakefile has:
> 
> CPPFLAGS        =       $(GDAL_INCLUDE) -DFRMT_ecw $(CPPFLAGS)
                 ^^^

I figured out that this needs to use the := operator instead. After that
it compiles fine.

For some .jp2 files gdalinfo doesn't return. For instance with 
ftp://ftp.remotesensing.org/jpeg2000/7sisters200.j2k I get:

$ gdalinfo 7sisters200.j2k
Driver: ECW/ERMapper Compressed Wavelets
Size is 1024, 692
Coordinate System is:
LOCAL_CS["RAW",
    UNIT["Meter",1]]
Origin = (0.000000,0.000000)
Pixel Size = (1.00000000,1.00000000)
Corner Coordinates:
Upper Left  (   0.0000000,   0.0000000)
Lower Left  (       0.000,     692.000)
Upper Right (    1024.000,       0.000)
Lower Right (    1024.000,     692.000)
Center      (     512.000,     346.000)
Band 1 Block=1024x1 Type=Byte, ColorInterp=Undefined
  Overviews: arbitrary
Band 2 Block=1024x1 Type=Byte, ColorInterp=Undefined
  Overviews: arbitrary
Band 3 Block=1024x1 Type=Byte, ColorInterp=Undefined
  Overviews: arbitrary

But I have to Ctrl-C to get back to the command line.

Also in QGIS, displaying any .jp2 file starts 100% CPU use and it
continues after the layer is rendered until the app is closed. I haven't
yet determined if this is the fault of QGIS, gdal, or ECW. But top
doesn't show anything as using much CPU.

Steve

> This seems like it should be easy to work around, but I'm not very wise
> in the ways of make.
> 
> Thanks,
> Steve
> 
> _______________________________________________
> Gdal-dev mailing list
> Gdal-dev at xserve.flids.com
> http://xserve.flids.com/mailman/listinfo/gdal-dev