[gdal-dev] Standard Dev. Environment?

[Ivan Lucena]

I always build with:

  --with-libz=internal \
  --with-png=internal \
  --with-libtiff=internal \
  --with-geotiff=internal \
  --with-jpeg=internal \
  --with-gif=internal \

 If that helps...

> Date: Fri, 10 Jan 2014 17:33:52 +0100
> From: even.rouault at mines-paris.org
> To: jlaura at asu.edu
> CC: gdal-dev at lists.osgeo.org
> Subject: Re: [gdal-dev] Standard Dev. Environment?
> 
> Jay,
> 
> hum it is well possible that the build with --without-jpeg doesn't work and that
> some drivers will try to use it. I haven't tried it for ages. GDAL has an
> internal version of libjpeg, so when you've no external libjpeg, that one will
> be picked up. I imagine that very few people test --without-jpeg.
> 
> Frank suggested you to just use plain "./configure". I'd recommend strongly that
> you just to try it. This must work well and autodetect which libs are available
> or not. The BuildingOnUnixWithMinimizedDrivers page you quote represents a
> non-standard configuration of GDAL, so you may hit rough corners.
> 
> To answer your question concerning the value for --with-jpeg, it is the
> installation prefix of libjpeg. Typically /usr for system jpeg (but that one
> would be picked up implicitely) or /usr/local (if you've installed your own
> libjpeg).
> 
> > Evan,
> >
> > Thanks for the info.  One more question for you - make clean worked, but I
> > have hit another issue:
> >
> > After running `./configure --without-jpeg ...`, `make clean`, `sudo make
> > install`:
> > ...
> > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to
> > `jpeg_write_scanlines'
> > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to
> > `jpeg_CreateCompress'
> > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to
> > `jpeg_read_scanlines'
> >
> > So lib-jpeg is seen.  This doesn't make sense since I have --without-jpeg
> > specified in the config.  I looked in the config and must have missed it -
> > does a flag to specify the full PATH to libjpeg exist?
> >
> > Thanks,
> > Jay
> >
> >
> > On Fri, Jan 10, 2014 at 7:24 AM, Even Rouault
> > <even.rouault at mines-paris.org>wrote:
> >
> > > Selon "Jay L." <jlaura at asu.edu>:
> > >
> > > > Frank,
> > > >
> > > > Thanks for the heads up.  I am using the --without-jasper flag as part of
> > > > the ./configure call.  Here is the error that I am seeing - that led to
> > > me
> > > > to believe that the issue is jasper related:
> > > >
> > > > make[1]: Entering directory `/home/vagrant/gdal-1.10.1/apps'
> > > > g++  gdalinfo.o commonutils.o  -L/home/vagrant/gdal-1.10.1 -lgdal
> > > >  -lpthread -lm -lrt -ldl                  -o gdalinfo
> > > > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to
> > > `dec_jpeg2000'
> > > > collect2: ld returned 1 exit status
> > > > make[1]: *** [gdalinfo] Error 1
> > > > make[1]: Leaving directory `/home/vagrant/gdal-1.10.1/apps'
> > > > make: *** [apps-target] Error 2
> > > >
> > > > I did install libjpeg-dev and libjasper-dev in hopes that this would
> > > > alleviate the issue.
> > > >
> > > > Perhaps I am pursuing the issue in the wrong direction?
> > >
> > > When you run ./configure several times, make sure to run "make clean"
> > > between
> > > the attempts. I'm not clear why you've had this error with the
> > > "dec_jpeg2000"
> > > symbol that is defined and used in the GRIB driver (it has a definition
> > > even if
> > > you don't have Jasper). Anway the "make clean" will probably solve it.
> > > Generally, "./configure" without any particular argument should work on
> > > most
> > > platforms.
> > >
> > > >
> > > > Thanks,
> > > > Jay
> > > >
> > > >
> > > > On Thu, Jan 9, 2014 at 9:33 PM, Frank Warmerdam <warmerdam at pobox.com>
> > > wrote:
> > > >
> > > > > Jay,
> > > > >
> > > > > Are you needing Jasper?  Normally a default build ("./configure")
> > > should
> > > > > work pretty well on a precise system. I'm guessing you have enabled
> > > jasper
> > > > > because it is key to what you want to do?  If not --without-jasper
> > > should
> > > > > be straight forward.
> > > > >
> > > > > Best regards,
> > > > > Frank
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Jan 9, 2014 at 8:00 PM, Jay L. <jlaura at asu.edu> wrote:
> > > > >
> > > > >> List,
> > > > >>
> > > > >> I wonder if a standard dev. environment exists?  I am working to
> > > extend a
> > > > >> driver and am having trouble getting an environment working that will
> > > > >> compile.  Current setup is a VagrantVM, Ubuntu 12.04 32-bit with
> > > source
> > > > >> downloaded from SVN.  Attempting to build with minimized
> > > > drivers<
> > > http://trac.osgeo.org/gdal/wiki/BuildingOnUnixWithMinimizedDrivers>as
> > > > per the build documentation and am having build errors due to
> > > > >> dec_jpeg2000 (jasper I believe).
> > > > >>
> > > > >> Q: Are devs using a standard environment (or a different flavor of
> > > *nix?)?
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> _______________________________________________
> > > > >> gdal-dev mailing list
> > > > >> gdal-dev at lists.osgeo.org
> > > > >> http://lists.osgeo.org/mailman/listinfo/gdal-dev
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > >
> > > >
> > >
> > ---------------------------------------+--------------------------------------
> > > > > I set the clouds in motion - turn up   | Frank Warmerdam,
> > > > > warmerdam at pobox.com
> > > > > light and sound - activate the windows | http://pobox.com/~warmerdam
> > > > > and watch the world go round - Rush    | Geospatial Software Developer
> > > > >
> > > >
> > >
> > >
> >
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20140110/4723e9ec/attachment.html>