Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Even Rouault
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, >

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Alan Boudreault
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 conf

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Jay L.
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 t

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread 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 integr

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Daniel Morissette
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 wrote

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Jay L.
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. Thanks Frank, Evan and Ivan. On Fri, Jan 10, 2014 at 9:54 AM, Ivan Lucena wrote: > I always build

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread 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.roua...@mines-paris.org > To: jla...@asu.edu > CC:

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Even Rouault
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

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Jay L.
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.

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Even Rouault
Selon "Jay L." : > 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++

Re: [gdal-dev] Standard Dev. Environment?

2014-01-10 Thread Jay L.
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/h

Re: [gdal-dev] Preferred XML parser

2014-01-10 Thread Even Rouault
Hi Pirmin, We have a variety of XML parsers used : - the built-in CPLMiniXML parser (port/cpl_minixml.h) that is a simple DOM parser without any fancy feature (it doesn't have explicit support for encodings for example. If you've need for recoding, you'll have to do it explicitely with CPLRecode()

[gdal-dev] Preferred XML parser

2014-01-10 Thread Pirmin Kalberer
Hi, I'm going to implement some more XML parsing in the Interlis driver. Which XML parser is generally suggested for using in OGR? For Interlis 2, we've implemented a SAX parser with Xerces, but for this part, only DOM access is needed. Regards Pirmin -- Pirmin Kalberer Sourcepole - Linux &