<HTML dir=ltr><HEAD><TITLE>Re: [GRASS-dev] Re: Building GRASS/QGIS with MSYS</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16587" name=GENERATOR><BASE href=http://mailstore.rossoalice.alice.it/exchange/Alice000000001264700/Bozze/R:%20[GRASS-dev]%20Re:%20Building%20GRASS_xF8FF_QGIS%20with%20MSYS.EML/1_text.htm></HEAD>
<BODY>
<DIV id=idOWAReplyText68131 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Thanks Benjamin,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#008000 size=2>>It's not. In fact, the GDAL developers recommend turning it off for<BR>>MSYS. As a consequence, you have to re-link the GDAL library files<BR>>after successful compilation in order to get shared Win32 DLLs.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Perfect!</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#008000 size=2>>I guess the guide assumes some software to be available in your MSYS<BR>>installation already. Do you require postgresql and python support?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>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!</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>To correctly build grass I installed postgresql, sqlite and tcl/tk before compiling it.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>But, also, the guide tells:</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr><FONT face=Arial><FONT color=#0000ff size=2>Since Quantum GIS needs GDAL with GRASS support, we need to compile GDAL <SPAN class=anchor id=line-903></SPAN>from source - Paul Kelly's package doesn't include GRASS support in GDAL. <SPAN class=anchor id=line-904></SPAN>The idea is following:</FONT></FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2>1. compile GDAL without GRASS</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2>2. compile GRASS</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2>3. compile GDAL with GRASS</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2>In step 1 the guide suggests to configure GDAL as follows:</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New"><FONT color=#0000ff><FONT size=2>./configure --prefix=/usr/local </FONT><FONT size=2>--enable-shared --without-libtool --disable-static --with-libz=/usr/local --with-png=/usr/local</FONT></FONT></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Then it tells:</FONT></DIV>
<DIV dir=ltr><PRE><FONT color=#0000ff><FONT face=Arial size=2>GDAL build procedure can be greatly simplified to use libtool with a libtool line patch: </FONT><FONT size=2><FONT face=Arial>configure gdal as below:</FONT></FONT></FONT></PRE></DIV>
<DIV dir=ltr><FONT size=2><FONT face=Arial><FONT face="Courier New" color=#0000ff>./configure --with-ngpython --with-xerces=/local/ --with-jasper=/local/ --with-grass=/local/grass-6.3.cvs/ --with-pg=/local/pgsql/bin/pg_config.exe</FONT></FONT></FONT></DIV>
<DIV dir=ltr><FONT color=#0000ff></FONT> </DIV>
<DIV dir=ltr><FONT size=2><FONT face=Arial><FONT color=#0000ff>Then fix libtool with: <SPAN class=anchor id=line-956></SPAN><FONT face="Courier New">mv libtool libtool.orig <SPAN class=anchor id=line-957></SPAN>cat libtool.orig | sed 's/max_cmd_len=8192/max_cmd_len=32768/g' > libtool</FONT> <SPAN class=anchor id=line-958></SPAN><SPAN class=anchor id=line-959></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr>
<P class=line874><FONT color=#0000ff><FONT size=2><FONT face=Arial>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. </FONT></FONT><FONT face=Arial size=2>Make and make install should be hassle free after this.</FONT></FONT></P>
<P class=line874><FONT face=Arial size=2>Probably last "./configure" and "sed" lines are supposed to be done if you set ./configure --with-libtool in the first step?</FONT></P>
<P class=line874><FONT face=Arial size=2>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).</FONT></P>
<P class=line874><FONT face=Arial size=2>Thanks,</FONT></P>
<P class=line874><FONT face=Arial size=2>MP</FONT></P>
<P class=line874>
<HR tabIndex=-1>
</P>
<P class=line874><FONT face=Tahoma size=2><B>Da:</B> grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke<BR><B>Inviato:</B> mar 05/02/2008 11.39<BR><B>Cc:</B> grass-dev@lists.osgeo.org<BR><B>Oggetto:</B> Re: [GRASS-dev] Re: Building GRASS/QGIS with MSYS<BR></FONT><BR></P></DIV></DIV>
<DIV>
<P><FONT size=2>> <BR>> Now the question: is with-libtool necessary for gdal? because there are<BR><BR>It's not. In fact, the GDAL developers recommend turning it off for<BR>MSYS. As a consequence, you have to re-link the GDAL library files<BR>after successful compilation in order to get shared Win32 DLLs.<BR><BR>> some things not clear to me about this passage.. after building gdal<BR>> level one, it says:<BR>> <BR>> ./configure --with-ngpython --with-xerces=/local/ --with-jasper=/local/<BR>> --with-grass=/local/grass-6.3.cvs/ --with-pg=/local/pgsql/bin/pg_config.exe<BR>> <BR>> 1) neither python nor grass and postgresql are install at this step of<BR>> the guide; how could that be? do I really need this "line" and the<BR>> following "sed"?<BR><BR>I guess the guide assumes some software to be available in your MSYS<BR>installation already. Do you require postgresql and python support?<BR><BR>> But also with the following warnings:<BR>> <BR>> configure: warning: *** Unable to locate iconv() function.<BR>> configure: warning: *** Unable to locate socket() function.<BR>> configure: warning: *** --with-opengl=windows is untested.<BR>> I decided to add Tcl/Tk support to be able to test some new grass<BR>> modules I added before to be "qgis ready";<BR><BR>Those are harmless as long as you don't need internationalized messages<BR>in GRASS.<BR><BR>Benjamin<BR>--<BR>Benjamin Ducke, M.A.<BR>Archäoinformatik<BR>(Archaeoinformation Science)<BR>Institut für Ur- und Frühgeschichte<BR>(Inst. of Prehistoric and Historic Archaeology)<BR>Christian-Albrechts-Universität zu Kiel<BR>Johanna-Mestorf-Straße 2-6<BR>D 24098 Kiel<BR>Germany<BR><BR>Tel.: ++49 (0)431 880-3378 / -3379<BR>Fax : ++49 (0)431 880-7300<BR>www.uni-kiel.de/ufg<BR><BR>_______________________________________________<BR>grass-dev mailing list<BR>grass-dev@lists.osgeo.org<BR><A href="http://lists.osgeo.org/mailman/listinfo/grass-dev">http://lists.osgeo.org/mailman/listinfo/grass-dev</A><BR></FONT></P></DIV></BODY></HTML>