[GRASS-user] OT: Tips for installing grass in archlinux
Ahmadou
dicko.ahmadou at gmail.com
Thu May 9 03:25:56 PDT 2013
Not sure if my approach is better but they are basically the same but I don't use virtualenv.
I first symlinked python2 and python2-config into $HOME/usr/bin as python and python-config.
Then to build GRASS, I do :
export PATH=$PATH:$HOME/usr/bin
./configure
make
make install
In a final step I created a launcher in bash named "grass"
#!/bin/bash
export PATH=$PATH:$HOME/usr/bin
python2 /usr/local/bin/grass70
To use GRASS7 I just type "grass"
On 9 mai 2013, at 07:47, tPietro <peter.zamb at gmail.com> wrote:
> Hi Ahmadou,
>
> On Thu, May 9, 2013 at 8:19 AM, Ahmadou Dicko <dicko.ahmadou at gmail.com> wrote:
>> I moved from Debian to ArchLinux and used to use GRASS 7 in Debian.
>> The main difference / problem when you want to install from source is
>> Python.
>>
>> In ArchLinux the default is Python is Python 3, so if you want to build
>> your own GRASS from scratch you have to use some tricks and tell GRASS to
>> use Python 2.
>
> I'm using virtualenv to isolate python2:
>
> $ virtualenv --system-site-packages -p python2.7 env-python2
>
> then I have to activate the virtualenv with:
>
> $ source ~/envs/env-python2/bin/activate
>
> I just put an alias on .bashrc:
>
> alias activate_python2='source ~/envs/env-python2/bin/activate'
> alias grass70='activate_python2 && python2
> ~/src/gis/grass/grass_trunk/bin.x86_64-unknown-linux-gnu/grass70
>
> therefore before compile grass I have to:
>
> $ activate_python2
> $ make
>
>> If someone is interested I can post how I succeed to build GRASS 7 in Arch
>
> I'm curious how do you solve it? may be there is a best way... :-)
>
> Best regards
>
> Pietro
More information about the grass-user
mailing list