Files
MX_Pmodule/olex2/modulefile
T
duan_j 1eb66c483b olex2: rewrite recipe for RHEL9 - official archive with GUI + olex2c
The official olex2-linux64.zip already ships both the GUI (olex2) and the
console build (olex2c) plus cctbx and a private CPython 3.8, so nothing is
compiled. Default prep downloads + sha256-verifies the zip (rolling file,
version carries the upstream SVN revision), install copies the vendor tree
flat into PREFIX and adds bin/olex2 + bin/olex2c launchers that reproduce
the vendor start env without running the unirun auto-updater.
2026-10-16 17:19:04 +02:00

28 lines
1.4 KiB
Plaintext

#%Module1.0
module-whatis "Olex2 - small-molecule structure solution, refinement and analysis: GUI (olex2) and console (olex2c)"
module-url "https://www.olexsys.org/olex2"
module-license "BSD - https://www.olexsys.org/olex2/docs/getting-started/installing-olex2/open-source/"
module-maintainer "MX Data <jiaxin.duan@psi.ch>"
module-help "
Olex2 is a free, open-source (BSD) package for determining, visualising and
analysing small-molecule crystal structures (solution, refinement with
olex2.refine/ShelXL, reports), built on cctbx/smtbx.
This module installs the official OlexSys Linux x86_64 distribution 1:1 and
puts two launchers on PATH:
olex2 the wxWidgets GUI (needs an X display; uses software OpenGL
by default, export LIBGL_ALWAYS_SOFTWARE=0 to override)
olex2c the console / headless Olex2 - same engine, same commands
(reap, refine, solve, ...), no GUI, scriptable in batch jobs.
Both set LD_LIBRARY_PATH/PYTHONHOME for the bundled CPython 3.8 and cctbx
and never run the vendor auto-updater (shared read-only install).
Per-user data (DataDir) lives in ~/.olex2. The vendor Python API (olx, olex
modules) is only available from inside olex2/olex2c, not as a system python.
"
# Launchers only: the raw binaries, the vendor 'start' script (auto-updater)
# and the private python live under $PREFIX root and stay off PATH.
prepend-path PATH $PREFIX/bin