Check your PATH Setting

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

Mac OS X Unix Tutorial Learning Unix for Mac OS X, 2nd Edition (Very basic treatment for an absolute beginner.) Mac OS X for Unix Geeks (introduce OS X to unix-oriented folks). Unix for Mac OS X: Visual QuickPro Guide - a couple of chapers are on line here: Unix for Mac OS X OS X Unleashed, 4th ed. (basic to advanced). Mac OS X juga memiliki.bashrc tetapi dengan nama yang berbeda yakni.profile sehingga kamu bisa melakukan perubahan pada.profile yang berada di user direktori, jika belum ada silahkan dibuat saja dan nanti file tersebut akan di-load otomatis. An exception to the terminal window guidelines is Mac OS X’s Terminal.app, which runs a login shell by default for each new terminal window, calling.bashprofile instead of.bashrc. Other GUI terminal emulators may do the same, but most tend not to. I don't run OS X.

20 responses to “A better bash prompt on Mac OS X”. By the way, the.bashrc file is executed for every shell and the.bashprofile is executed only when you login. So you typically put stuff in the.bashprofile that you only want to see once, and stuff in your.bashrc.

Make sure Dakota executables (and optionally test files and current directory) are available on the PATH by typing 'which dakota' at command line prompt. If your PATH variable is set correctly, the path to the dakota binary should be displayed.

If your PATH variable is NOT set correctly, you will get a message like the following:

The following setup will make the dakota command and other helper programs available at the terminal. If you prefer you may refer to the dakota executable using its fully-qualified path. Note, however, that some examples will require modification to work properly if dakota and related helper programs are not on your PATH.

To persist the PATH to Dakota across terminals/sessions, make the following changes to the appropriate shell login script. If you prefer to just test in your current terminal, execute the commands directly in a terminal.

Make Changes in Bash Shell

Edit your Bash startup file in your favorite text editor. For Linux, this is ~/.bashrc. OS X terminal runs a login shell, and so the start up file may be ~/.bashrc, ~/.bash_profile, ~/.bash_login, or ~/.profile. See the manpage for Bash for more information about the differences between login and non-login shells.
Modify and export PATH, PYTHONPATH, and (if using a Dakota release prior to 6.8) (DY)LD_LIBRARY_PATH variables. Type the following line, replacing $INSTALL_DIR with the absolute path to your installation directory, e.g. $HOME. 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.
On Linux:
On OS X:
Save and close file.
Update changes in your shell window.

Bashrc For Mac Os X 10.10

Source Bashrc Macos

Make Changes in C shell

Bashrc For Mac Os X 10.7

Edit the startup file ~/.cshrc in your favorite text editor.
Modify and export PATH, PYTHONPATH, and (if using a Dakota release prior to 6.8) (DY)LD_LIBRARY_PATH variables. Type the following line, replacing $INSTALL_DIR with the absolute path to your installation directory, e.g. $HOME. 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.
On Linux:
On OS X:
Save and close file.
Update changes in your shell window.