R: [GRASS-dev] Re: Building GRASS/QGIS with MSYS

[Benjamin Ducke]

> Probably last "./configure" and "sed" lines are supposed to be done if
> you set ./configure --with-libtool in the first step?

Yes, that's what I would assume. Without libtool, you have to to delete
the static libs and exe tools and re-link everything for stage one and
two -- tedious but works.

> 
> So the real question is: does GDAL need ngpython, xerces, jasper and
> postresql? (I know grass is needed, but the guide suggest to build GDAL
> first without it, and then rebuild it with grass support enabled).

GDAL needs none of those for the basic libraries to build. Xerces is an
XML parser. It's needed for GDAL to be able and access web mapping
services. NGPython is for GDAL Python bindings. Only interesting if you
intend to directly script-programm GDAL using Python. Jasper adds
another raster image format support to GDAL.

You have to first build and install GDAL without GRASS support.
Then configure and build GRASS (it will detect GDAL correctly and enable
GDAL support, even though no GRASS support is enabled in GDAL at this
stage!). Install GRASS. Then  reconfigure GDAL with GRASS support, build
and install again. That should do it.

Benjamin

> 
> Thanks,
> 
> MP
> 
> ------------------------------------------------------------------------
> 
> *Da:* grass-dev-bounces at lists.osgeo.org per conto di Benjamin Ducke
> *Inviato:* mar 05/02/2008 11.39
> *Cc:* grass-dev at lists.osgeo.org
> *Oggetto:* Re: [GRASS-dev] Re: Building GRASS/QGIS with MSYS
> 
>> 
>> Now the question: is with-libtool necessary for gdal? because there are
> 
> It's not. In fact, the GDAL developers recommend turning it off for
> MSYS. As a consequence, you have to re-link the GDAL library files
> after successful compilation in order to get shared Win32 DLLs.
> 
>> some things not clear to me about this passage.. after building gdal
>> level one, it says:
>> 
>> ./configure --with-ngpython --with-xerces=/local/ --with-jasper=/local/
>> --with-grass=/local/grass-6.3.cvs/
> --with-pg=/local/pgsql/bin/pg_config.exe
>> 
>> 1) neither python nor grass and postgresql are install at this step of
>> the guide; how could that be? do I really need this "line" and the
>> following "sed"?
> 
> I guess the guide assumes some software to be available in your MSYS
> installation already. Do you require postgresql and python support?
> 
>> But also with the following warnings:
>> 
>> configure: warning: *** Unable to locate iconv() function.
>> configure: warning: *** Unable to locate socket() function.
>> configure: warning: *** --with-opengl=windows is untested.
>> I decided to add Tcl/Tk support to be able to test some new grass
>> modules I added before to be "qgis ready";
> 
> Those are harmless as long as you don't need internationalized messages
> in GRASS.
> 
> Benjamin
> --
> Benjamin Ducke, M.A.
> Archäoinformatik
> (Archaeoinformation Science)
> Institut für Ur- und Frühgeschichte
> (Inst. of Prehistoric and Historic Archaeology)
> Christian-Albrechts-Universität zu Kiel
> Johanna-Mestorf-Straße 2-6
> D 24098 Kiel
> Germany
> 
> Tel.: ++49 (0)431 880-3378 / -3379
> Fax : ++49 (0)431 880-7300
> www.uni-kiel.de/ufg
> 
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
> 

-- 
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg