#OS X SHELL SCRIPT IN GLOBAL INSTALL#

Edit the startup file ~/.cshrc in your favorite text editor.

$ source ~/.bashrc # Or other startup file on OS X # All versions, to use the dakota.interfacing Python module:Įxport PYTHONPATH=$PYTHONPATH:$INSTALL_DIR/share/dakota/PythonĮxport PATH=$INSTALL_DIR/bin:$INSTALL_DIR/share/dakota/test:$INSTALL_DIR/gui/Contents/MacOS:$PATHĮxport PATH=$INSTALL_DIR/bin:$INSTALL_DIR/test:$INSTALL_DIR/gui/DakotaUI.app/Contents/MacOS:$PATHĮxport DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:$INSTALL_DIR/lib:$INSTALL_DIR/bin You need not add the gui path if you are not using the Dakota GUI, or PYTHONPATH if you do not plan to use the dakota.interfacing Python module.Įxport PATH=$INSTALL_DIR/bin:$INSTALL_DIR/share/dakota/test:$INSTALL_DIR/gui:$PATHĮxport PATH=$INSTALL_DIR/bin:$INSTALL_DIR/test:$INSTALL_DIR/gui:$PATHĮxport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INSTALL_DIR/lib:$INSTALL_DIR/bin Type the following line, replacing $INSTALL_DIR with the absolute path to your installation directory, e.g.

Modify and export PATH, PYTHONPATH, and (if using a Dakota release prior to 6.8) (DY)LD_LIBRARY_PATH variables.

See the manpage for Bash for more information about the differences between login and non-login shells. In general functions (and scripts) are more powerful and versatile than aliases, but aliases provide and easy and comparatively safe way to customize the your shell environment.

OS X terminal runs a login shell, and so the start up file may be ~/.bashrc, ~/.bash_profile, ~/.bash_login, or ~/.profile. Since a function or script could not change the directory for the current shell, you have to use alias substitution to get the cd. Edit your Bash startup file in your favorite text editor.If you prefer to just test in your current terminal, execute the commands directly in a terminal. To persist the PATH to Dakota across terminals/sessions, make the following changes to the appropriate shell login script. Note, however, that some examples will require modification to work properly if dakota and related helper programs are not on your PATH. If you prefer you may refer to the dakota executable using its fully-qualified path. In the new shell script, delete the text and replace it with: cd Start in my home directory. In the next list, find Run Shell Script and drag it into the workflow area on the right. The following setup will make the dakota command and other helper programs available at the terminal. Select the document type Application and click Choose. Leave the Shell at ‘/bin/bash’ but set the ‘Pass Input’ option to ‘as arguments.’ Replace the default. Search for the ‘Run Shell Script’ action and double click to add to the workflow. usr/bin/which: no dakota in (/usr/local/bin:/usr/local/sbin) Leave the settings to work on ‘text’ in ‘any application’. If your PATH variable is NOT set correctly, you will get a message like the following: path/to/dakota/install/directory/bin/dakota If your PATH variable is set correctly, the path to the dakota binary should be displayed.

Make sure Dakota executables (and optionally test files and current directory) are available on the PATH by typing 'which dakota' at command line prompt.

#OS X SHELL SCRIPT IN GLOBAL INSTALL#

In the instructions below, $INSTALL_DIR refers to the path to the new install directory, /path/to/dakota/install/directory/Dakota.

Os x shell script in global