jpeg-turbo mit Homebrew installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• tjbench

Projektgeschichte

The project traces its ancestry to libjpeg/SIMD, an MMX-accelerated derivative of libjpeg v6b by Miyasaka Masaru. The libjpeg-turbo project page says TigerVNC and VirtualGL made numerous enhancements in 2009, and libjpeg-turbo spun off as an independent project in early 2010 to make high-speed JPEG compression and decompression broadly available.

The 1.0.0 SourceForge archive shows source and binary packages dated 2010-07-02, including Unix, Windows, and macOS artifacts. The project later moved official releases to GitHub and packagecloud/APT repositories, with the homepage recording that move on 2023-11-29.

Adoptionsgeschichte

libjpeg-turbo spread because it preserves the familiar libjpeg API while delivering much higher speed on common CPU architectures. The upstream documentation describes both the traditional libjpeg API and the simpler TurboJPEG API, and notes optional compatibility with libjpeg v7 and v8 ABIs.

In 2019, libjpeg-turbo became an ISO/IEC and ITU-T reference implementation of the JPEG standard, giving it standards significance in addition to its practical packaging role.

Wie es verwendet wird

Packages and applications use libjpeg-turbo either through the libjpeg-compatible API, the TurboJPEG API, or command-line tools such as cjpeg, djpeg, jpegtran, rdjpgcom, wrjpgcom, and tjbench. The library is used for both compression and decompression, with color-space extensions for common RGB/BGR buffer layouts.

Warum Paket-Nerds sich dafür interessieren

For package maintainers, libjpeg-turbo is a classic performance replacement package: it can sit under image viewers, browsers, desktop stacks, scientific tools, and language bindings while keeping libjpeg compatibility expectations intact.

Its significance is also political in the package ecosystem. Choosing libjpeg-turbo over IJG libjpeg is often a distro-level or dependency-level decision that trades strict upstream lineage for speed, compatibility, and broad real-world adoption.

Zeitleiste

• 2009: TigerVNC and VirtualGL made major enhancements to libjpeg/SIMD.
• 2010: libjpeg-turbo spun off as an independent project.
• 2010: Version 1.0.0 source and binary artifacts appeared in the SourceForge file archive on July 2.
• 2013: libjpeg-turbo 1.3 added in-memory source and destination manager functions without requiring libjpeg v8 API/ABI emulation.
• 2019: libjpeg-turbo became an official ISO/IEC and ITU-T reference implementation of JPEG.
• 2023: Official releases moved to GitHub and packagecloud/APT repositories.
• 2026: The GitHub release page listed 3.2.0 with release assets dated June 30.

Related projects

• libjpeg-turbo descends from libjpeg/SIMD and remains API-compatible with IJG libjpeg v6b.
• TigerVNC and VirtualGL were early project antecedents through their 2009 codec work.
• The TurboJPEG API is the project's simpler companion API alongside the traditional libjpeg API.
• mozjpeg and IJG libjpeg are adjacent JPEG codec projects in packaging decisions.

Quellen

• https://formulae.brew.sh/formula/jpeg-turbo
• https://github.com/libjpeg-turbo/libjpeg-turbo
• https://github.com/libjpeg-turbo/libjpeg-turbo#readme
• https://github.com/libjpeg-turbo/libjpeg-turbo/releases
• https://libjpeg-turbo.org/
• https://sourceforge.net/projects/libjpeg-turbo/files/1.0.0/