[GRASSLIST:462] Re: Building GRASS in a user account

[David Finlayson]

Thanks Aaron and Glynn, that did the trick (LD_LIBRARY_PATH was
necessary to for GRASS to find proj4 libs).  It took me a while to
build proj, fftw, gdal and grass but it appears to have compiled
correctly. Now, sqlite, and back to gdal to fix the grass
dependency...

Thanks again,

David

On 3/28/06, Glynn Clements <glynn at gclements.plus.com> wrote:
>
> David Finlayson wrote:
>
> > In the past, I've always had root access to install libraries via the
> > package managers prior to building GRASS from CVS. I am now facing a
> > system where I will not have root access period. In fact, I cannot
> > even use CVS since the firewall blocks most ports (I tried the https
> > trick by adding 443 at the end of the IP address, but I don't think it
> > is supported by CVSROOT.
> >
> > So, I created a source directory in my user account and downloaded
> > grass and proj4. Proj4 built without problems. But how do I "install"
> > it in my user account? That is, where do I put the files (and what is
> > the best way to get them there) so that I can build GRASS against the
> > proj4 headers and libraries?
>
> Put them wherever you want. It will probably help to create a personal
> "root" directory in your home directory which will serve as the root
> for all self-installed packages.
>
> E.g. if you use ~/local, configure packages such as proj using
> --prefix=$HOME/local ("~" doesn't work in the middle of an argument,
> but "$HOME" does) to get headers and libraries into ~/local/include
> and ~/local/lib, then use --with-includes=$HOME/local/include and
> --with-libs=$HOME/local/lib when configuring GRASS.
>
> You will probably also need to set LD_LIBRARY_PATH to your personal
> library directory to get shared libraries to work.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
>


--
David Finlayson