Skip to content

Packaging scripts to prebuild libvips and its dependencies - you're probably looking for https://github.com/lovell/sharp

License

Notifications You must be signed in to change notification settings

lovell/sharp-libvips

Folders and files

NameName
Last commit message
Last commit date

Latest commit

78d9ab4 · Mar 8, 2021
Mar 7, 2021
Mar 8, 2021
Feb 13, 2021
Jun 25, 2020
Mar 8, 2021
Mar 8, 2021
Mar 8, 2021
Feb 27, 2021
Mar 1, 2021
Feb 22, 2021
Sep 22, 2017
Oct 17, 2020
Jun 25, 2020
Mar 6, 2021
Sep 22, 2017
Mar 1, 2021
Mar 6, 2021
Mar 5, 2021
Sep 22, 2017
Sep 22, 2017

Repository files navigation

Packaging scripts

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

During npm install, these binaries are fetched as tarballs from this repository via HTTPS and stored locally within node_modules/sharp/vendor.

The base URL can be overridden using the npm_config_sharp_libvips_binary_host environment variable.

https://sharp.pixelplumbing.com/install#custom-prebuilt-binaries

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.

Windows

The output of libvips' build-win64-mxe "web" target is post-processed within multiple containers.

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 be the relative @rpath using install_name_tool.

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.