[gdal-dev] Vagrant developement environment
Ari Jolma
ari.jolma at gmail.com
Wed Apr 9 11:06:01 PDT 2014
On 04/09/2014 08:09 PM, Even Rouault wrote:
> Le mercredi 09 avril 2014 19:01:55, Ari Jolma a écrit :
>> On 04/09/2014 05:49 PM, Even Rouault wrote:
>>> 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
>> May I ask, what was this issue?
> I didn't really investigate. Likely "make generate" not done when you build
> from a fresh svn checkout.
I tested and found out that it was the order of things in GNUmakefile
for target build. Now it checks first the wrappers and generates them
unless they exist.
Wrapper generation requires swig of course.
Ari
More information about the gdal-dev
mailing list