| Both sides previous revision Previous revision Next revision | Previous revision |
| technical:recipes:software-managment [2021-04-28 14:04] – [VALET Setup] anita | technical:recipes:software-managment [2024-01-04 16:48] (current) – [Builds] frey |
|---|
| Each of the compilers chosen in building //variants// of the 5.1.0 release will follow the same general procedure. | Each of the compilers chosen in building //variants// of the 5.1.0 release will follow the same general procedure. |
| |
| <note>The notation '':'' (colon) in output examples throughout this document indicates lines of output displayed from the command entered.</note> | <note>The notation '':'' (colon) in output examples throughout this document indicates lines of output are displayed by the command entered but have been omitted from this documentation.</note> |
| |
| ==== System GCC ==== | ==== System GCC ==== |
| on DARWIN and in | on DARWIN and in |
| <code bash> | <code bash> |
| [user@login00.darwin ~]$ VALET_PKG_DIR="$WORKDIR_SW/valet" ; VALET_PKG_DIR_MODE=2770 | [user@login00.darwin ~]$ VALET_PKG_DIR="$WORKDIR/sw/valet" ; VALET_PKG_DIR_MODE=2770 |
| </code> | </code> |
| on Caviness. | on Caviness. |
| <code bash> | <code bash> |
| [user@login00.darwin ~]$ mkdir -p --mode=$VALET_PKG_DIR_MODE "$VALET_PKG_DIR" | [user@login00.darwin ~]$ mkdir -p --mode=$VALET_PKG_DIR_MODE "$VALET_PKG_DIR" |
| </code | </code> |
| |
| VALET allows package definitions in a variety of formats (XML, JSON, YAML) but YAML tends to be the simplest format so we will use it here. | VALET allows package definitions in a variety of formats (XML, JSON, YAML) but YAML tends to be the simplest format so we will use it here. |
| </code> | </code> |
| As mentioned at the start of this document, the ''$LIBXC_PREFIX'' can be particularly helpful when configuring an Autoconf or CMake build of software that depends on this version/variant of **libxc**. The development context is the most common use of context in VALET that it can be shortened from ''vpkg_require --context=development'' to just ''vpkg_devrequire''. | As mentioned at the start of this document, the ''$LIBXC_PREFIX'' can be particularly helpful when configuring an Autoconf or CMake build of software that depends on this version/variant of **libxc**. The development context is the most common use of context in VALET that it can be shortened from ''vpkg_require --context=development'' to just ''vpkg_devrequire''. |
| | |
| | ===== Recipes for Specific Software ===== |
| | |
| | All recipes are provided based on a specific cluster, Caviness and/or DARWIN. However each recipe may be used as a reference from one cluster to another by using the appropriate file system (directory structure) and VALET packages for the cluster you are trying to install the software. |
| | |
| | ==== MCFOST ==== |
| | [[technical:recipes:mcfost|Building MCFOST on Caviness]] |
| | |
| | |
| | ==== Python ==== |
| | |
| | * [[technical:recipes:pyqt5-in-virtualenv|Building PyQt5 in a Python Virtual Environment]] |
| | * [[technical:recipes:jupyter-notebook|Jupyter Notebook Python Virtual Environment]] |
| | * [[technical:recipes:keras-in-virtualenv|Keras Python Virtual Environment]] |
| | * Gurobi Python Virtual Environments |
| | * [[software:gurobi:caviness#serial-or-threaded-python-environment|Gurobi Python Threaded and Serial]] |
| | * [[software:gurobi:caviness#mpi-python-environment|Gurobi Python MPI]] |
| | * [[technical:recipes:emcee-in-virtualenv|Python Virtualenv: emcee and pyKLIP]] |
| | * [[technical:recipes:mpi4py-in-virtualenv|Python Virtual Environments with mpi4py]] |
| | * [[technical:recipes:tensorflow-in-virtualenv|TensorFlow Python Virtual Environment]] |
| | |
| | ==== WRF ==== |
| | |
| | * [[software:wrf:caviness|WRF on Caviness]] |
| | * [[software:wrf:darwin|WRF on DARWIN]] |
| | |
| | ==== VASP ==== |
| | [[technical:recipes:vasp-6-darwin|Building VASP 6 on Caviness/DARWIN]] |
| | |