<br>Perhaps you have added it after the call to Init.sh? It needs to be set before Init.sh is run in order to be picked up.<div><br></div><div>My grass64 is like this now:</div><div><div>trap "echo 'User break!' ; exit" 2 3 9 15</div>
<div>GRASS_ADDON_PATH=/usr/local/myproj</div><div>export GRASS_ADDON_PATH</div><div># Set the GISBASE variable</div><div>GISBASE=/usr/local/grass-6.4.0svn</div><div>export GISBASE</div><div>exec "$GISBASE/etc/Init.sh" "$@"</div>
</div><div><br></div><div>So it's defined before Init.sh.</div><div>If I do echo "$GRASS_ADDON_PATH it appears in GRASS so it's parsed inside grass.</div><div><br></div><div>Regarding your suggestion:</div><div>
sudo GRASS_ADDON_PATH=/usr/local/myproject grass64 -wxpython</div><div>I got the same result. An Error Window and the same command-output error.</div><div><br></div><div>Again, I think this might be an error associated with g.parse since he recognize that the script exists but he is not building Form and he is runned automatically when I insert its name in the command line</div>
<div><br></div><div>Regarding your .profile suggestion, what is necessary to be in that .profile file? and where should it be?</div><div><br></div><div>Franz</div><div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Even easier though, would be to set it in your .profile file in your home directory (create it if it's not there) - then it will always be set whenever you start a new shell and there is no need to edit the GRASS startup script. If you upgrade to a newer version of GRASS you won't need to re-edit the startup script either. Or you could just specify it on the command-line before starting GRASS; something like:<br>
paul@haptimap:~/gis$ GRASS_ADDON_PATH=/usr/local/myproject grass64<br>
should also work.<br>
<br>
Best regards<br><font color="#888888">
<br>
Paul<br>
</font></blockquote></div><br></div>