# sharp-libvips **Repository Path**: wu_xiaole/sharp-libvips ## Basic Information - **Project Name**: sharp-libvips - **Description**: No description available - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2024-05-21 - **Last Updated**: 2024-05-21 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # 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](npm) and published to the npm registry under the [@img](https://www.npmjs.com/org/img) organisation. ## Creating a tarball Most people will not need to do this; proceed with caution. Run the top-level [build script](build.sh) without parameters for help. ### Linux One [build script](build/lin.sh) is used to (cross-)compile the same shared libraries within multiple containers. * [x64 glibc](platforms/linux-x64/Dockerfile) * [x64 musl](platforms/linuxmusl-x64/Dockerfile) * [ARMv6 glibc](platforms/linux-armv6/Dockerfile) * [ARMv7-A glibc](platforms/linux-armv7/Dockerfile) * [ARM64v8-A glibc](platforms/linux-arm64v8/Dockerfile) * [ARM64v8-A musl](platforms/linuxmusl-arm64v8/Dockerfile) * [s390x glibc](platforms/linux-s390x/Dockerfile) ### Windows The output of libvips' [build-win64-mxe](https://github.com/libvips/build-win64-mxe) static "web" releases are [post-processed](build/win.sh) within a [container](platforms/win32/Dockerfile). ### 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](https://github.com/kleisauke/wasm-vips) are [used to compile](build/wasm.sh) 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](LICENSE). The shared libraries contained in the tarballs are distributed under the terms of [various licences](THIRD-PARTY-NOTICES.md), all of which are compatible with the Apache 2.0 Licence.