Installer cairo avec Homebrew

Liens du projet

• Page d'accueil

Commandes et alias

• cairo-trace

Historique du projet

The official repository README says cairo was originally developed by Carl Worth and Keith Packard. Cairo's early identity was a cross-device vector rendering library: the documentation archive points to a 2003 paper under the earlier Xr name and later cairo presentations from 2005.

The 1.0.0 release announcement on 2005-08-24 marked the stable API/ABI line for 1.x.y releases. At that point xlib, image, and win32 were supported backends, while Glitz, PostScript, PDF, Quartz, and XCB were experimental. Modern project documentation lists a wider set of supported targets, including PDF, PostScript, SVG, Quartz, Win32, Xlib, and XCB.

Cairo is tied closely to pixman for pixel compositing and to desktop text/rendering stacks through fontconfig, FreeType, platform font backends, and toolkit bindings. The project continues to publish releases through cairographics.org, with the official news page listing releases up to 1.18.4 in 2025.

Historique d'adoption

Cairo became infrastructure rather than an end-user app. The official bindings page lists bindings for languages including C++, Haskell, Java, Perl, PHP, Python, Ruby, and others, and notes toolkit integration such as GTK+ 2.8+ support. That binding and toolkit spread made cairo a common dependency in Linux desktop, document, plotting, and image-generation software.

Package-manager adoption is broad: the input facts list Cairo across Homebrew, Debian/Ubuntu, Fedora, Alpine, Arch, MacPorts, Nix, and openSUSE-style packaging. That breadth reflects cairo's role as a shared graphics primitive for higher-level applications.

Modes d'utilisation

Developers use cairo to draw vector graphics, text, paths, patterns, and transformed/composited images to screen and file surfaces. Common package builds enable image, PNG, PDF, PostScript, SVG, Xlib, XCB, FreeType, fontconfig, Quartz, or Windows backends depending on platform needs.

The Homebrew package exposes cairo-trace, but most users consume cairo as a library dependency through headers, pkg-config metadata, and language bindings.

Pourquoi les passionnés de paquets s'y intéressent

Cairo is one of those packages that explains why dependency graphs get deep: a small API surface at the application level hides years of rendering, font, backend, and platform compatibility work. For package nerds it is a foundational desktop graphics dependency, sitting between low-level raster compositing in pixman and higher-level toolkits, browsers, plotting libraries, and document renderers.

Its dual LGPL/MPL licensing, stable 1.x compatibility promise, backend matrix, and language bindings made it unusually reusable across open-source desktop stacks and proprietary-friendly distribution scenarios.

Chronologie

• 2003: Xr-era cross-device vector rendering work precedes the cairo name.
• 2005: cairo 1.0.0 released with a stable 1.x compatibility promise.
• 2008: cairo 1.8.0 release appears in the official news archive.
• 2018: cairo 1.16.0 released.
• 2023: cairo 1.18.0 released.
• 2025: cairo 1.18.4 released.

Related projects

• pixman is the pixel-manipulation library used by cairo for image compositing.
• Language bindings and adjacent projects include pycairo, cairomm, rcairo, cairo-perl, cairo-ocaml, and cairocffi.
• GTK and other GUI toolkits use cairo as a drawing layer; cairo also targets document formats such as PDF, PostScript, and SVG.

Sources

• https://gitlab.freedesktop.org/cairo/cairo/-/blob/master/README.md
• https://www.cairographics.org/
• https://www.cairographics.org/bindings/
• https://www.cairographics.org/documentation/
• https://www.cairographics.org/news/
• https://www.cairographics.org/news/cairo-1.0.0/