Skip to content

[package list]

nlohmann-json

License information

The nlohmann-json class is licensed under the MIT License. The license can also be found on the "License" page of the project web site which also contains additional information about liciensing of components used from elsewhere.

See also the "License" section of the README in the GitHub repository, LICENSE.MIT file in that repository and the LICENSES subdirectory for other licenses.

After loading the module, the LICENSE.MIT file can also be found in the directory $EBROOTNLOHMANNMINJSON/share/licenses/nlohmann-json.

Pre-installed modules (and EasyConfigs)

To access module help and find out for which stacks and partitions the module is installed, use module spider nlohmann-json/<version>.

EasyConfig:

User-installable modules (and EasyConfigs)

Install with the EasyBuild-user module:

eb <easyconfig> -r
To access module help after installation and get reminded for which stacks and partitions the module is installed, use module spider nlohmann-json/<version>.

EasyConfig:

Technical documentation (central installation)

EasyBuild

Version 3.10.4 for CPE 22.08

  • Based on the JSC easyconfig

Version 3.11.2 for CPE 22.12 and 23.09

  • Based on the JSC easyconfig

Version 3.11.3 from CPE 23.12 on

  • Moved to the LUMI-SoftwareStack repository from LUMI-EasyBuild-contributed as it is needed to build another library that is in the main software stack.

  • Had to move to 3.11.3 already in 23.12 rather than following the 2023a EasyBuild release as 3.11.2 did not compile with the Cray compiler.

Technical documentation (user EasyBuild installation)

EasyBuild

Version 3.10.4 for CPE 22.08

  • Based on the JSC easyconfig

Version 3.11.2 for CPE 22.12 and 23.09

  • Based on the JSC easyconfig

Archived EasyConfigs

The EasyConfigs below are additonal easyconfigs that are not directly available on the system for installation. Users are advised to use the newer ones and these archived ones are unsupported. They are still provided as a source of information should you need this, e.g., to understand the configuration that was used for earlier work on the system.