This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
sysadminfaq [2015/03/26 17:02] admin [II. Building Modules] |
sysadminfaq [2015/03/26 17:04] admin [II. Building Modules] |
||
---|---|---|---|
Line 12: | Line 12: | ||
Modules are pretty easy when you get the hang of them. Basically all these ''%%$<VARIABLES>%%'' can be set in them, so that the user doesn't have to have big ''%%.bashrc%%'' entries. \\ As a starting point, look into the existing modulefiles at ''%%/cm/shared/modulefiles%%''. Whatever is listed here get read out on a ''%%module avail%%'' call. \\ | Modules are pretty easy when you get the hang of them. Basically all these ''%%$<VARIABLES>%%'' can be set in them, so that the user doesn't have to have big ''%%.bashrc%%'' entries. \\ As a starting point, look into the existing modulefiles at ''%%/cm/shared/modulefiles%%''. Whatever is listed here get read out on a ''%%module avail%%'' call. \\ | ||
- | To write your own modules, take an existing modulefile (for all that \\tcl\\ messaging at the beginning), and modify it according to [[http://modules.sourceforge.net/man/modulefile.html | this handy information]]. | + | To write your own modules, take an existing modulefile (for all that //tcl// messaging at the beginning), and modify it according to [[http://modules.sourceforge.net/man/modulefile.html | this handy information]]. A workable template goes something like: \\ |
+ | <code tcl> | ||
+ | Blah. | ||
+ | </code> | ||
------------------------- | ------------------------- |