[GRASS-dev] GRASS_EXTRA_PATHS and GRASS_EXTRA_LIBS for importing
extra working environments?
Alessandro Frigeri
afrigeri at unipg.it
Tue Apr 13 10:35:07 EDT 2010
Hi Glynn,
The use of ~/.grass.bashrc is the perfect solution to my problem.
Thanks for the hint!
Regards,
Alessandro
2010/4/9 Glynn Clements <glynn at gclements.plus.com>:
>
> Alessandro Frigeri wrote:
>
>> At the moment I'm using system's LD_LIBRARY_PATH for adding specific
>> extra libs, and GRASS_ADDON_PATH to add extra scripts and executables I
>> want to use within GRASS GIS.
>>
>> Especially for the case of some specific libraries, these are mostly
>> useful within the data analysis session -- and are not useful as
>> system-wide libraries, so I ended up with a custom Init.sh script that
>> set them for me within the GRASS session.
>
> Note that you can use ~/.grass.bashrc for commands which are to be run
> at the beginning of a GRASS session.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
>
>
--
Alessandro Frigeri, PhD
More information about the grass-dev
mailing list