2014 17:33:52 +0100
From: even.roua...@mines-paris.org
To: jla...@asu.edu
CC: gdal-dev@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
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
Selon Jay L. jla...@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'
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'
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
: gdal-dev@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
...@asu.edu
CC: gdal-dev@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
On 14-01-10 1:23 PM, Jay L. wrote:
Success. Ivan, I used your ./configure flags - stock was also not
working on this VM.
I wonder if the dev. community is large enough to warrant storing a
lightweight Vagrant box image somewhere.
Talking of Vagrant, FYI about a year ago Alan Boudreault
The github: https://github.com/aboudreault/mapserver_dev-cookbook
Note that I started to upgrade the environment to be compatible with the
latest vagrant. I will also update the README file in the repo since the
procedure will be easier (since a few things I was using have been
directly
Have you also seen the geobox environment?
https://github.com/zhm/geobox
The install fails as the links to postgres configs are outdated (GiST URL
changes) Alan, if you have no issue, I might fork geobox and swap in your
PostGreSQL lines to get geobox back up and running. I think it is easier
Yeah, np. My repo only aims for mapserver development. Geobox installs a
lot more stuff, which is not really needed for our stuff.
Alan
On 14-01-10 02:44 PM, Jay L. wrote:
Have you also seen the geobox environment?
https://github.com/zhm/geobox
The install fails as the links to postgres
Le vendredi 10 janvier 2014 17:33:52, Even Rouault a écrit :
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
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
13 matches
Mail list logo
