4953c55ad5
With hat: portmgr Sponsored by: Absolight
31 lines
1.1 KiB
Text
31 lines
1.1 KiB
Text
|
|
######################################################################
|
|
|
|
Unlike to windows systems, saga_cmd should be instantly available in
|
|
the shell as it is usually installed in %%PREFIX%%/bin.
|
|
|
|
Next you have to set the environmental variable SAGA_MLB to make SAGA
|
|
know where the SAGA module libraries exist on your system. You can do
|
|
this permanently by adding the following command to your .bashrc file
|
|
or by defining it temporarily on the command line before executing
|
|
SAGA CMD:
|
|
|
|
export SAGA_MLB=/yourPathToSAGA_modules
|
|
|
|
e.g.:
|
|
export SAGA_MLB=%%PREFIX%%/lib/saga
|
|
|
|
Now your system is prepared for using SAGA CMD to execute SAGA
|
|
modules.
|
|
|
|
######################################################################
|
|
|
|
Since version 2.1.0 it is not necessary any more, to use a leading
|
|
"lib" for module library names on Unix-like systems. Now you will have
|
|
to alter back your scripts by removing "lib" from the name (like it is
|
|
on MS Windows).
|
|
|
|
e.g.:
|
|
saga_cmd ta_morphometry instead of saga_cmd libta_morphometry
|
|
|
|
######################################################################
|