This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
mesa [2025/04/30 11:01] – created jansen | mesa [2025/04/30 11:37] (current) – [No setup needed, nor wanted!!] jansen | ||
---|---|---|---|
Line 33: | Line 33: | ||
or in '' | or in '' | ||
alias mesainit " | alias mesainit " | ||
- | For your personal MESA installes, the same method can be used, with the alias pointing to the '' | + | For your personal MESA installs, the same method can be used, with the alias pointing to the '' |
For users of the bash shell: | For users of the bash shell: | ||
- | export MESASDK_ROOT==/ | + | export MESASDK_ROOT=/ |
export MESA_DIR=/ | export MESA_DIR=/ | ||
alias mesainit " | alias mesainit " | ||
Line 45: | Line 45: | ||
Of course, make sure you replace the path names from this example with the actual location where you have installed the software! | Of course, make sure you replace the path names from this example with the actual location where you have installed the software! | ||
- | And, when editing session startup files like '' | + | And, when editing session startup files like '' |
- | A simple way to test your setup is to run the shell from the commandline | + | A simple way to test your setup is to run the shell from the command line with the '' |
'' | '' | ||
or | or | ||
'' | '' | ||
Any errors will be displayed in your terminal, so you can fix them before they block you from further logins. | Any errors will be displayed in your terminal, so you can fix them before they block you from further logins. | ||
+ | |||
+ | Yet another methoud would be, to include the setenv (or export) commands and the source command into a small text file or script, and load that file when you want to activate the MESA environment, | ||
+ | setenv MESASDK_ROOT / | ||
+ | setenv MESA_DIR / | ||
+ | source $MESASDK_ROOT/ | ||
+ | And when you want to active your MESA environment, | ||
+ | |||
====== Links ====== | ====== Links ====== |