Skip to content

v0.12.5

Choose a tag to compare

@github-actions github-actions released this 22 Jul 04:11
· 76 commits to main since this release

Added

  • Self-contained libtfs-deps-<ver>-<platform> release packages (transitive static libs) — consumers need no vcpkg on the prebuilt path.

Release artifacts

Per-platform packages (platform ids: linux-gnu-x86_64, linux-gnu-arm64,
linux-musl-x86_64, macos-arm64, macos-x86_64, windows-ucrt64):

  • libtfs-<version>-<platform>.tar.gz (.zip on Windows):
    • lib/libtfs.a — the libtfs static library
    • lib/libtebako_dirent_helper_c.a — C helper archive (link dependency
      of libtfs where the legacy tebako API is built; not shipped on Windows)
    • include/tebako/** — public headers
    • lib/cmake/libtfs/ — CMake package config (find_package(libtfs))
  • libtfs-deps-<version>-<platform>.tar.gz (all platforms): the
    transitive static libraries consumers link against —
    libdwarfs_reader, libdwarfs_common, libdwarfs_metadata_legacy,
    libdwarfs_decompressor, libflatbuffers, libzip, libfmt,
    libxxhash, libzstd, liblz4, liblzma, brotli (dec/enc/common),
    libz, libbz2, libboost_filesystem, libboost_chrono, plus
    libcrypto/libssl on Linux and Windows (macOS consumers link
    brew/system OpenSSL at link time) — with the CMake package configs
    of those ports under share/ (or lib/cmake/ where a port installs
    there), so find_dependency can still resolve.
  • mkdwarfs-<platform> and tebakofs-<platform> — command-line tools
    (.exe suffix on windows-ucrt64)

Self-contained consumption: a libtfs-<version>-<platform>
package plus the matching libtfs-deps-<version>-<platform> package
are fully self-contained — linking libtfs.a needs no vcpkg (and no
C++20 dependency build) on the consumer machine, only a linker and
the platform system libraries (plus brew/system OpenSSL on macOS).
Consumers that prefer to resolve dependencies themselves (e.g. their
own vcpkg) can keep using the libtfs package alone.

Linkage notes (from the shipped binaries' ldd/objdump output):

  • All C/C++ third-party dependencies (dwarfs-t, libzip, fmt,
    jemalloc, Boost, …) are statically linked into the binaries on
    every platform.
  • linux-gnu-*: dynamic glibc/libstdc++ (built on ubuntu-24.04;
    requires glibc ≥ 2.38 at runtime, e.g. Ubuntu 24.04 or newer).
  • linux-musl-x86_64: dynamic musl libc + libstdc++/libgcc_s (built
    on Alpine 3.21; on a minimal Alpine install: apk add libstdc++ libgcc).
  • macos-*: dynamic macOS system libraries only (libSystem, libc++;
    built on macos-14 / macos-15-intel).
  • windows-ucrt64: dynamic UCRT + MSYS2 runtime DLLs
    (libgcc_s_seh-1.dll, plus libwinpthread-1.dll/libstdc++-6.dll
    for mkdwarfs); run inside MSYS2 UCRT64 or ship those DLLs alongside.

The Windows package ships the modern C/C++ API only (the legacy tebako
API needs the ruby build context).

SquashFS: shipped artifacts are built WITH_SQUASHFS=OFF — the
backends are dwarfs + zip only, so consumers are not forced to link
LGPL squashfs-tools-ng. POSIX source builds may opt into the SquashFS
backend (LGPL) with -DWITH_SQUASHFS=ON.

SHA-256 checksums for all artifacts: see the SHA256SUMS asset.