libvips and its dependencies are provided as pre-compiled shared libraries for the most common operating systems and CPU architectures.
During packaging of NetVips, these binaries are fetched as tarballs from
this repository via HTTPS and stored within the NuGet package (see
Build.cs
for details).
Finally, the created .nupkg are uploaded on NuGet. You can find them here:
- NetVips.Native.win-x64
- NetVips.Native.win-x86
- NetVips.Native.win-arm64
- NetVips.Native.linux-x64
- NetVips.Native.linux-arm
- NetVips.Native.linux-arm64
- NetVips.Native.linux-musl-x64
- NetVips.Native.linux-musl-arm64
- NetVips.Native.osx-x64
- NetVips.Native.osx-arm64
The version number of these NuGet packages is in sync with libvips' version number.
Most people will not need to do this; proceed with caution.
Run the top-level build script without parameters for help.
One build script is used to (cross-)compile the same shared libraries within multiple containers.
The output of libvips' build-win64-mxe static "web" releases are post-processed within a container.
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 @loader_path with install_name_tool.
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.