Anyone. As the OpenJPEG code is released under the BSD 2-clause “Simplified” License, anyone can use or modify the code, even for commercial applications. The only restriction is to retain the copyright in the sources or in the binaries documentation. Of course, if you modified the code in a way that might be of interest for other users, you are encouraged to share it (through a github pull request or by filling an issue) but this is not a requirement.
API Documentation needs a major refactoring. Meanwhile, you can check installation instructions and codec documentation.
The library is developed and maintained by the Image and Signal Processing Group (ISPGroup), in the Université catholique de Louvain (UCL, with the support of the CNES, the CS company and the intoPIX company. The JPWL module has been developed by the Digital Signal Processing Lab (DSPLab) of the University of Perugia, Italy (UNIPG).
See LICENSE for license and copyright information.
See INSTALL for installation procedures.
See NEWS for user visible changes in successive releases.
The openjpwl, openjp3d and openmj2 components have been removed after the 2.4.0 release. Their building and working state is unknown. People interested in them should start from the 2.4.0 tag.
An API/ABI timeline is automatically updated here.
OpenJPEG strives to provide a stable API/ABI for your applications. As such it only exposes a limited subset of its functions. It uses a mechanism of exporting/hiding functions. If you are unsure which functions you can use in your applications, you should compile OpenJPEG using something similar to gcc:
-fvisibility=hidden compilation flag. See also: http://gcc.gnu.org/wiki/Visibility
On windows, MSVC directly supports export/hiding function and as such the only API available is the one supported by OpenJPEG.