[gdal-dev] Vagrant developement environment

[Even Rouault]

Le mardi 08 avril 2014 06:49:36, Ivan Lucena a écrit :
> Hi Howard,
> 
> I started it all over and I got it to work.
> 
> When I logged with "vagrant ssh" this time the gdal folder was there but
> not installed yet.
> 
> And I didn't have development tools build GDAL, so I run "sudo sh
> posinstall.sh" and I also installed "make" and "perl" by hand and after
> that I got a clean GDAL installation.
> 
> Ha, I also needed to install the GDAL-Python "by hand".

When rebuilding from scratch, I could see that there was indeed an issue  with 
Perl bindings. I've disabled them. So "vagrant up" show work OK

> 
> I can see that it could be a nice environment to run GDAL autotest, if I
> could add some SDK dependent driver.

You can add custom scripts to install the SDK and list them in Vagrantfile, and 
edit gdal.sh to build against the additional SDKs.

> 
> What else can we do with that thing? How does PDAL take advantage of
> Vagrant anyway?
> 
> Ivan
> 
> > From: howard at hobu.co
> > Date: Mon, 7 Apr 2014 11:09:09 -0500
> > To: gdal-dev at lists.osgeo.org
> > Subject: Re: [gdal-dev] Vagrant developement environment
> > 
> > On Apr 7, 2014, at 5:57 AM, Even Rouault <even.rouault at mines-paris.org> 
wrote:
> > > vagrant provision
> > 
> > If you get stuck with vagrant, on prescribed chicken-waving exercise is
> > to simply do 'vagrant destroy' of the vm and then 'vagrant up' again.
> > 'vagrant provision' will still have the effects of partially Maybe some
> > prerequisite didn't couldn't be built because of network access or
> > something. _______________________________________________
> > gdal-dev mailing list
> > gdal-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/gdal-dev√√

-- 
Geospatial professional services
http://even.rouault.free.fr/services.html