[GRASS-dev] Add /usr/local/bin and /lib to PATH var building WinGRASS

GRASS GIS GRASS GIS developer
1

Hi,

why do I need to add /usr/local/bin and /usr/local/lib to PATH variable before to build GRASS (as suggested by Paul Kelly’s notes)?

Regards

Marco

2

On Wed, 27 Feb 2008 marco.pasetti@alice.it wrote:

Hi,

why do I need to add /usr/local/bin and /usr/local/lib to PATH variable before to build GRASS (as suggested by Paul Kelly's notes)?

During GRASS compilation, after each module is compiled it is run with the --html-description command-line option, to generate part of the man pages. You need to have any DLLs the modules depend on in the PATH so that the modules will run correctly. It is not needed for compiling though - the locations specified using --with-*-libs to configure are used for compiling. So if you don't have the DLLs in the PATH then you won't be able to generate the man pages properly; that's all.

Paul

3

Hi Paul,

thanks for the explanation! :wink:
I build a brand new MSYS environment for the compilation of GRASS, updating libraries with latest releases and adding libtiff support (I succesfully built also libjpeg, but some tests gave me errors, thus I decided to not include its support)
in GRASS configure I used --with-libs=/usr/local/lib, even if all dlls are now in /usr/local/bin, because each dll has a related import static library in /usr/local/lib
now I’m facing python and wxputhon support in RC5… that it seems to be a big, big problem!!!

Thanks

Marco

Da: Paul Kelly [mailto:paul-grass@stjohnspoint.co.uk]
Inviato: mer 27/02/2008 13.17
A: marco.pasetti@alice.it
Cc: grass-dev@lists.osgeo.org
Oggetto: Re: [GRASS-dev] Add /usr/local/bin and /lib to PATH var building WinGRASS

On Wed, 27 Feb 2008 marco.pasetti@alice.it wrote:

Hi,

why do I need to add /usr/local/bin and /usr/local/lib to PATH variable before to build GRASS (as suggested by Paul Kelly’s notes)?

During GRASS compilation, after each module is compiled it is run with the
–html-description command-line option, to generate part of the man pages.
You need to have any DLLs the modules depend on in the PATH so that the
modules will run correctly. It is not needed for compiling though - the
locations specified using --with-*-libs to configure are used for
compiling. So if you don’t have the DLLs in the PATH then you won’t be
able to generate the man pages properly; that’s all.

Paul