Dear Mathijs, You might be facing this issue if you are executing the application using the scripts, such as run_saga_app, present in bin directory of installation. I think you can get rid of SAGA_LOCATION variable by doing a little change inside the script. For example in run_saga_app script, the first few lines check if the SAGA_LOCATION variable has been defined, if not then the script asks for that. One solution could be to remove those lines from the script and replace "$SAGA_LOCATION" with absolute path of saga installation. Another way could be to define a new variable and make changes inside the script according to the newly defined variable. cheers, yasir On Wed, Oct 15, 2008 at 1:10 PM, Mathijs den Burger <mathijs@cs.vu.nl>wrote:
Hi all,
Both the C++ implementation and the Java implementation of SAGA use the environment variable SAGA_LOCATION to point to the location of the SAGA installation. Right now, it is therefore impossible to use both the C++ and Java SAGA implementation simultaneously without changing SAGA_LOCATION all the time. Even worse, future SAGA implementations may also reuse SAGA_LOCATION.
It seems desirable to avoid such clashes between multiple SAGA installations in general. What would be the best generic way to accomplish that? Should the SAGA spec define a global environment variable namespace (e.g. LSU_C++_SAGA_LOCATION, VU_JAVA_SAGA_LOCATION)? And are such environment variables really needed in all implementations in the first place?
regards, Mathijs
-- saga-rg mailing list saga-rg@ogf.org http://www.ogf.org/mailman/listinfo/saga-rg