Difference: MakingSoftwareAvailableUsingLMOD (5 vs. 6)

Revision 62017-02-17 - MartinMarinus

Line: 1 to 1
 
META TOPICPARENT name="SoftwareInstallation"

Howto create your own/group software modules

Introduction

Line: 50 to 50
  local version = "VERSION"
Changed:
<
<
--local base = "/hpc/local/\$MY_DISTRO/\$MY_GROUP/software/PROGRAM-" .. version local base = "\$HOME/\$MY_DISTRO/software/PROGRAM-" .. version
>
>
local base = "/hpc/local/\$MY_DISTRO/\$MY_GROUP/software/PROGRAM-" .. version
  conflict("PROGRAM")
Line: 67 to 66
 

remarks

  • In lua lines starting with -- are interpreted as comments
Deleted:
<
<
  • "--local base" in this example shows the path in which the program should be installed to make it group accessible. In such case the module file should be written to /hpc/local/$MY_DISTRO/$MY_GROUP/etc/modulefiles/PROGRAM/VERSION.lua
 
  • The number of environment variables that need to be set (prepend_path lines) to make your program running depends on the needs of your program.
  • If the program of requires another software module (e.g. a particular Java) to be loaded, this can be automated by adding lines like lines like:
load("Java/1.8.0_60")
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback