Packaging scripts

libvips and its dependencies are provided as pre-compiled shared libraries for the most common operating systems and CPU architectures.

These are packaged and published to the npm registry under the @img organisation.

Creating a tarball

Most people will not need to do this; proceed with caution.

Run the top-level build script without parameters for help.

Linux

One build script is used to (cross-)compile the same shared libraries within multiple containers.

• x64 glibc
• x64 musl
• ARMv6 glibc
• ARM64v8-A glibc
• ARM64v8-A musl
• ppc64le glibc
• s390x glibc

Windows

The output of libvips' build-win64-mxe static "web" releases are post-processed within a container.

macOS

Uses a macOS virtual machine hosted by GitHub to compile the shared libraries. The dylib files are compiled within the same build script as Linux.

• x64 (native)
• ARM64 (cross-compiled)

Dependency paths are modified to use the relative @rpath with install_name_tool.

WebAssembly

The scripts from wasm-vips are used to compile libvips and its dependencies as static Wasm libraries ready for further compilation into a single, statically-linked sharp shared library.

Licences

These scripts are licensed under the terms of the Apache 2.0 Licence.

The shared libraries contained in the tarballs are distributed under the terms of various licences, all of which are compatible with the Apache 2.0 Licence.