Skip to content

[package list]

JasPer

License information

JasPer license information is avaialble in the LICENSE.txt and COPYRIGHT.txt files in the JasPer GitHub repository.

From LUMI/23.12 on, these files can also be found in the $EBROOTJASPER/share/licenses/JasPer subdirectory after loading the module.

Pre-installed modules (and EasyConfigs)

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

EasyConfig:

Technical documentation (central installation)

General notes

  • Some programs that come with JasPer require GLUT. These are not built.

  • JasPer now also supports HEIC but that support is not included in our builds.

EasyBuild

2.0.33 from CPE 21.06 on

  • The EasyConfig is derived from the University of Antwerpen one with a version bump and change of download location.

3.0.4 from CPE 22.06 on

  • Trivial version bump of the EasyConfig

  • Did a check of the tests in the log file and there don't seem to be any new optional dependencies.

Version 4.0.0 from CPE 22.12 on

  • Trivial version bump of the EasyConfig, but we did copy the improved sanity check from the EasyBuilders version.

  • For LUMI/23.12, license information was added to the installation and the sanity checks were improved.

Version 4.2.5 from CPE 25.03 on

  • Trivial port of the EasyConfig for 4.0.0 for 24.03/24.11.

Version 4.2.8 in 25.09

  • Trivial port of the EasyConfig for 4.2.5 in 25.03.

  • Switched to the new EasyConfig parameters.

Version 4.2.9 from 26.03 on

  • Started as a trivial port of the EasyConfig for 4.2.8 in 25.09.

  • However, we added support for the HEIC image format which pulled in a lot of additional dependencies, moving this package to the back of the build chain.

Archived EasyConfigs

The EasyConfigs below are additional 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.