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

GRASS GIS GRASS GIS developer
, ,
1

Hi Tisham,

There are some issues with GDAL support on MINGW so the little ‘sed’ line hacks the libtool to work properly.
Please let me know if you need help with any particular steps.
Regards,
Tishampati Dhar

I built all following the wiki, using Paul Kelly’s prebuilt extralibs and your suggestions about gdal, grass-6.3.0RC4 and qgis 0.9.1, but I have linking problems (procedure entry point X509_STORE_set_flags could not be located in the dynamic link library libeay32.dll), so I decided to restart to build all. Probably I found some “things to change” in the wiki, but I don’t want to overbalance since I check everithing is working…

Now the question: is with-libtool necessary for gdal? because there are 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”?
  2. the same problem comes at the end of gdal level two… same questions :wink:

after that… I configured grass as follow:

export PATH=“/usr/local/bin:/usr/local/lib:$PATH”
./configure --prefix=/usr/local --bindir=/usr/local
–with-includes=/usr/local/include --with-libs=/usr/local/lib
–with-cxx --without-jpeg --without-tiff
–with-postgres --with-postgres-includes=/usr/local/pgsql/include --with-postgres-libs=/usr/local/pgsql/lib
–with-opengl=windows --with-fftw
–with-freetype --with-freetype-includes=/usr/local/include/freetype2
–without-x
–with-tcltk --with-tcltk-includes=/c/programmi/tcl/include --with-tcltk-libs=/c/programmi/tcl/bin
–enable-x11=no --enable-shared=yes --with-proj-share=/usr/local/share/proj
–with-sqlite --with-sqlite-includes=/usr/local/include --with-sqlite-libs=/usr/local/lib

with this result:

GRASS is now configured for: i686-pc-mingw32
Source directory: /usr/local/src/grass-6.3.0RC4
Build directory: /usr/local/src/grass-6.3.0RC4
Installation directory: ${prefix}/grass-6.3.0RC4
Startup script in directory: /usr/local
C compiler: gcc -g -O2
C++ compiler: c++ -g -O2
Building shared libraries: yes
64bit support: no
OpenGL platform: Windows
NVIZ: yes
BLAS support: no
C++ support: yes
DWG support: no
FFMPEG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GLw support: no
JPEG support: no
LAPACK support: no
Large File Support (LFS): yes
Motif support: no
MySQL support: no
NLS support: no
ODBC support: no
OGR support: yes
OpenGL support: yes
PNG support: yes
PostgreSQL support: yes
Python support: no
Readline support: no
SQLite support: yes
Tcl/Tk support: yes
TIFF support: no
X11 support: no
MacOSX application: no

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”;

Thanks for your support,

Marco

2

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

3

Thanks Benjamin,

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.

Perfect!

I guess the guide assumes some software to be available in your MSYS
installation already. Do you require postgresql and python support?

It’s a guide bug, I suppose. The guide tells to install postgresql just at the end of msys environment building (after gdal, grass, and other steps…), but it fails!
To correctly build grass I installed postgresql, sqlite and tcl/tk before compiling it.
But, also, the guide tells:

Since Quantum GIS needs GDAL with GRASS support, we need to compile GDAL from source - Paul Kelly’s package doesn’t include GRASS support in GDAL. The idea is following:

  1. compile GDAL without GRASS
  2. compile GRASS
  3. compile GDAL with GRASS

In step 1 the guide suggests to configure GDAL as follows:

./configure --prefix=/usr/local --enable-shared --without-libtool --disable-static --with-libz=/usr/local --with-png=/usr/local

Then it tells:

GDAL build procedure can be greatly simplified to use libtool with a libtool line patch: configure gdal as below:

./configure --with-ngpython --with-xerces=/local/ --with-jasper=/local/ --with-grass=/local/grass-6.3.cvs/ --with-pg=/local/pgsql/bin/pg_config.exe

Then fix libtool with: mv libtool libtool.orig cat libtool.orig | sed ‘s/max_cmd_len=8192/max_cmd_len=32768/g’ > libtool

Libtool on windows assumes a line length limit of 8192 for some reason and tries to page the linking and fails miserably. This is a work around. Make and make install should be hassle free after this.

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

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).

Thanks,

MP

Da: grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
Inviato: mar 05/02/2008 11.39
Cc: grass-dev@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@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

4

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@lists.osgeo.org per conto di Benjamin Ducke
*Inviato:* mar 05/02/2008 11.39
*Cc:* grass-dev@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@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

5

the last doubt is if those options are needed for qgis+grass building.
I'all ask to qgis-dev

They aren't.

another questions: reading BuildingWindowsBinaryOnLinux QgisWiki, I
noticed that the guide tells to build all the libs (XDR, ZLIB, PROJ.4
first, included in Paul Kelly's prebuilt-package, and then GEOS, GSL,
EXPAT, PostgreSQL, GDAL and SQLite) before to build GRASS, while the
WindowsWiki tells to build/install GEOS, GSL, EXPAT, PostgreSQL and
SQLite after GRASS and GDAL "Level Two"; could that be another
WinGrassWiki bug? (I'm sure now that PostgreSQL and SQLite are needed
before GRASS build!)

Neitjer PostgreSQL nor SQLite are needed for a basic version of
QGIS+GRASS. All other libraries are needed by either GRASS or GDAL
or both to be installed first.

If you want support for SQLite and PostgreSQL and GRASS, you need
to have them installed first, as well.

Benjamin

Many thanks. Best Regards,

MP

------------------------------------------------------------------------
*Da:* grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
*Inviato:* mar 05/02/2008 12.35
*A:* GRASS devel
*Oggetto:* Re: R: [GRASS-dev] Re: Building GRASS/QGIS with MSYS

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@lists.osgeo.org per conto di Benjamin Ducke
*Inviato:* mar 05/02/2008 11.39
*Cc:* grass-dev@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@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

_______________________________________________
grass-dev mailing list
grass-dev@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

6

On 05/02/08 10:40, marco.pasetti@alice.it wrote:

after that... I configured grass as follow:

[...]

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.

These are all normal.

Moritz

7

Thanks again,

I’ll rebuild a brand new msys environment, with the following sequece:

  1. Flex and Bison
  2. Paul Kelly’s precompiled grass-extralibs, including:
  • zlib.1.2.3
  • libpng-1.2.16-noconfig
  • xdr-4.0-mingw2
  • freetype-2.3.4
  • fftw-2.1.5
  • PDCurses-3.1
  • proj-4.5.0
  • gdal-1.4.1
  1. GEOS
  2. SQLite
  3. GSL
  4. Expat
  5. PostgreSQL
  6. GDAL Level One
  7. Tcl/Tk
  8. GRASS (with postgresql, sqlite and tcl/tk support enabled)
  9. GDAL Level Two

Best Regards,

MP

Da: grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
Inviato: mar 05/02/2008 13.39
A: GRASS devel
Oggetto: Re: R: R: [GRASS-dev] Re: Building GRASS/QGIS with MSYS

the last doubt is if those options are needed for qgis+grass building.
I’all ask to qgis-dev

They aren’t.

another questions: reading BuildingWindowsBinaryOnLinux QgisWiki, I
noticed that the guide tells to build all the libs (XDR, ZLIB, PROJ.4
first, included in Paul Kelly’s prebuilt-package, and then GEOS, GSL,
EXPAT, PostgreSQL, GDAL and SQLite) before to build GRASS, while the
WindowsWiki tells to build/install GEOS, GSL, EXPAT, PostgreSQL and
SQLite after GRASS and GDAL “Level Two”; could that be another
WinGrassWiki bug? (I’m sure now that PostgreSQL and SQLite are needed
before GRASS build!)

Neitjer PostgreSQL nor SQLite are needed for a basic version of
QGIS+GRASS. All other libraries are needed by either GRASS or GDAL
or both to be installed first.

If you want support for SQLite and PostgreSQL and GRASS, you need
to have them installed first, as well.

Benjamin

Many thanks. Best Regards,

MP

Da: grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
Inviato: mar 05/02/2008 12.35
A: GRASS devel
Oggetto: Re: R: [GRASS-dev] Re: Building GRASS/QGIS with MSYS

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@lists.osgeo.org per conto di Benjamin Ducke
Inviato: mar 05/02/2008 11.39
Cc: grass-dev@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@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

grass-dev mailing list
grass-dev@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

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

8

Benjamin Ducke wrote:

> 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.

iconv isn't necessarily required for localised messages. At least,
GRASS doesn't use it explicitly; it uses libintl (typically from GNU
gettext), which may use iconv internally.

The only GRASS code which uses iconv() directly is the FreeType text
rendering code in the display system. FreeType indexes glyphs by their
Unicode codepoint.

If you have iconv, any text will be converted from the encoding
specified by $GRASS_ENCODING or "d.font charset=". If you don't have
iconv, all text is assumed to be encoded in ISO-8859-1 (the first 256
Unicode codepoints correspond to ISO-8859-1).

--
Glynn Clements <glynn@gclements.plus.com>

9

Hi,

about the last mail, I’m workig on step 8.
I report that (if previously installed) GEOS support must be disabled in GDAL; it makes building to fail!
Not sure, but actually possible, either SQLite and PostgreSQL should be disabled too.
For secure (and not time-wasting) procedure, I built GDAL without GEOS, SQLite and PostgreSQL.
If GEOS is certainly to set as disabled, no tests have been done enabling SQLite and PostgreSQL; however those two last are not required in GDAL building, even if required (and then enbled) in GRASS building (thanks Moritz).

I worked with 1.4.1 version of GDAL. It would be interesting to do some testings using latest version of GDAL (1.5), which, as it seems, introduces new useful features.

Regards and thanks all for your support (specially Benjamin, Moritz and Glynn; many thanks)

MP

Da: grass-dev-bounces@lists.osgeo.org per conto di marco.pasetti@alice.it
Inviato: mar 05/02/2008 14.39
A: grass-dev@lists.osgeo.org
Oggetto: R: R: R: [GRASS-dev] Re: Building GRASS/QGIS with MSYS

Thanks again,

I’ll rebuild a brand new msys environment, with the following sequece:

  1. Flex and Bison
  2. Paul Kelly’s precompiled grass-extralibs, including:
  • zlib.1.2.3
  • libpng-1.2.16-noconfig
  • xdr-4.0-mingw2
  • freetype-2.3.4
  • fftw-2.1.5
  • PDCurses-3.1
  • proj-4.5.0
  • gdal-1.4.1
  1. GEOS
  2. SQLite
  3. GSL
  4. Expat
  5. PostgreSQL
  6. GDAL Level One
  7. Tcl/Tk
  8. GRASS (with postgresql, sqlite and tcl/tk support enabled)
  9. GDAL Level Two

Best Regards,

MP

Da: grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
Inviato: mar 05/02/2008 13.39
A: GRASS devel
Oggetto: Re: R: R: [GRASS-dev] Re: Building GRASS/QGIS with MSYS

the last doubt is if those options are needed for qgis+grass building.
I’all ask to qgis-dev

They aren’t.

another questions: reading BuildingWindowsBinaryOnLinux QgisWiki, I
noticed that the guide tells to build all the libs (XDR, ZLIB, PROJ.4
first, included in Paul Kelly’s prebuilt-package, and then GEOS, GSL,
EXPAT, PostgreSQL, GDAL and SQLite) before to build GRASS, while the
WindowsWiki tells to build/install GEOS, GSL, EXPAT, PostgreSQL and
SQLite after GRASS and GDAL “Level Two”; could that be another
WinGrassWiki bug? (I’m sure now that PostgreSQL and SQLite are needed
before GRASS build!)

Neitjer PostgreSQL nor SQLite are needed for a basic version of
QGIS+GRASS. All other libraries are needed by either GRASS or GDAL
or both to be installed first.

If you want support for SQLite and PostgreSQL and GRASS, you need
to have them installed first, as well.

Benjamin

Many thanks. Best Regards,

MP

Da: grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
Inviato: mar 05/02/2008 12.35
A: GRASS devel
Oggetto: Re: R: [GRASS-dev] Re: Building GRASS/QGIS with MSYS

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@lists.osgeo.org per conto di Benjamin Ducke
Inviato: mar 05/02/2008 11.39
Cc: grass-dev@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@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

grass-dev mailing list
grass-dev@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

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

10

Benjamin wrote:

> 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.

Hi,

I don't know much about building these things for MS-Windows, but it
has been my understanding that for the last year or two the above
recommendation has changed. Now it looks like:

- Build GDAL without GRASS support
- BUild GRASS based on that GDAL
- Build the GDAL GRASS plugin based on that GRASS

It's a bit simpler and auto-build friendly.

download the plugin:
  ftp://ftp.remotesensing.org/gdal/gdal-grass-1.4.3.tar.gz

Hamish

      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ