libTIFF

Packages

Install

Install the variant for the platform you build, declare it as a dependency in crossbind.config.js and import the header from JavaScript. Nothing is compiled on your machine. A project that builds for several platforms lists one variant per platform: @crossbind/port-tiff-wasi, @crossbind/port-tiff-android, @crossbind/port-tiff-ios are published too.

Header import paths are relative to the package's dist/prebuilt/<target>/include, so @crossbind/port-tiff/<header>.h is upstream's own header. The full flow, including what the meta package is for, is in the Libraries guide.

WASI command tools

18 upstream commands ship as npm executables built for wasm32-wasip3. They need wasmtime on PATH and no compiler - see WASI commands.

• fax2ps-wasi
• fax2tiff-wasi
• pal2rgb-wasi
• ppm2tiff-wasi
• raw2tiff-wasi
• tiff2bw-wasi
• tiff2pdf-wasi
• tiff2ps-wasi
• tiff2rgba-wasi
• tiffcmp-wasi
• tiffcp-wasi
• tiffcrop-wasi
• tiffdither-wasi
• tiffdump-wasi
• tiffinfo-wasi
• tiffmedian-wasi
• tiffset-wasi
• tiffsplit-wasi

Licence

• npm license field of @crossbind/port-tiff: libtiff.
• The -bin-wasi package lists every statically linked component in its own license field, which is longer than the library licence above.
• The licence files that ship with the package, and the port recipe, are in the port directory.

Facts on this page come from the port manifests in the repository and from what npm served on beta when the site was built. See the Libraries guide for the full consumer flow.