int2dds_ffi_vendor

ROS 2 vendor package that fetches the prebuilt int2DDS FFI library for the host platform at build time and exposes it to colcon/ament as an imported CMake target. It is the dependency boundary between the Rust int2DDS core (shipped as prebuilt binaries) and the C++ rmw_int2dds_cpp middleware.

What it does

1. Detects the host OS, architecture, and libc (gnu/musl).
2. Downloads the release asset for that OS, architecture and libc from the int2DDS releases page.
3. Reads the manifest in the archive and verifies the library’s sha256.
4. Installs int2dds-ffi.h + the platform shared library as include/ + lib/ (on Windows the DLL goes to bin/ and the import library to lib/).
5. Exports the imported target int2dds_ffi::int2dds_ffi.

Consuming it (downstream)

find_package(int2dds_ffi_vendor REQUIRED)
target_link_libraries(my_target int2dds_ffi::int2dds_ffi)

<!-- package.xml -->
<depend>int2dds_ffi_vendor</depend>

Release asset layout

The int2DDS release tagged v${INT2DDS_FFI_VERSION} (see CMakeLists.txt) publishes one archive per OS and architecture: int2dds-<version>-<dist>.tar.gz (.zip on Windows), where <dist> is linux-x86_64, linux-x86_64-musl, linux-aarch64, linux-aarch64-musl, linux-armhf, linux-armhf-musl, windows-x86_64, windows-aarch64, macos-x86_64 or macos-arm64. The Linux library carries the usual SONAME symlink chain:

int2dds-<version>-linux-x86_64.tar.gz
└── int2dds-<version>-linux-x86_64/
    ├── include/int2dds-ffi.h                  # C API header
    ├── lib/
    │   ├── libint2dds_ffi.so.<version>        #   real file
    │   ├── libint2dds_ffi.so.0 -> .so.<version>  # SONAME
    │   └── libint2dds_ffi.so   -> .so.0       #   linker name
    ├── manifest.txt                           # dist + sha256 + soname + min_glibc
    └── LICENSE

On Windows the DLL is bin/int2dds_ffi.dll and the import library lib/int2dds_ffi.dll.lib (installed as lib/int2dds_ffi.lib).

manifest.txt:

name: int2dds
version: "0.1.8"
api_header: int2dds-ffi.h
license: Apache-2.0
triple: x86_64-unknown-linux-gnu
dist: linux-x86_64
sha256: <hex>
soname: libint2dds_ffi.so.0
min_glibc: "2.28"

The vendor package checks that dist: matches the archive it selected and that sha256: matches the library, so no SHA values need to be hard-coded here.

libc selection

The default is glibc (gnu), which is what ROS binaries target. Each gnu archive’s manifest.txt names the oldest glibc it runs on (min_glibc). For a musl host:

colcon build --cmake-args -DINT2DDS_FFI_LIBC=musl

Every Linux architecture, armhf included, has a musl archive.

Building against a locally built FFI

INT2DDS_FFI_TARBALL replaces the download with an archive you already have — an int2DDS release archive for the host, or one with the same layout:

colcon build --cmake-args \
  -DINT2DDS_FFI_TARBALL=/path/to/int2dds-0.1.8-linux-x86_64.tar.gz

Two reasons to reach for it. The obvious one is offline builds. The other is that the release tag does not identify the ABI: the v0.1.1 assets were rebuilt in place, so two different int2dds-ffi.h files have shipped under that one version, and because the manifest is rebuilt along with them the sha256 check cannot separate the two either. Naming the file is the only way to be sure which build you linked against.

File truncated at 100 lines see the full file

Changelog for package int2dds_ffi_vendor

0.1.8 (2026-10-07)

• Vendor the int2DDS FFI 0.1.8 release assets in place of 0.1.7. The libraries are a fresh build, so the sha256 of every artifact moved.
• The soname is unchanged at libint2dds_ffi.so.0.
• Contributors: Intellectus Corp.

0.1.7 (2026-09-23)

• Vendor the int2DDS FFI 0.1.7 release assets in place of 0.1.6. The libraries are a fresh build, so the sha256 of every artifact moved.
• The soname is unchanged at libint2dds_ffi.so.0.
• Contributors: Intellectus Corp.

0.1.6 (2026-09-22)

• Vendor the int2DDS FFI 0.1.6 release assets in place of 0.1.5. The libraries are a fresh build, so the sha256 of every artifact moved.
• The soname is unchanged at libint2dds_ffi.so.0.
• Contributors: Intellectus Corp.

0.1.5 (2026-09-10)

• Vendor the int2DDS FFI 0.1.5 release assets in place of 0.1.4. The libraries are a fresh build, so the sha256 of every artifact moved.
• The soname is unchanged at libint2dds_ffi.so.0.
• Contributors: Intellectus Corp.

0.1.4 (2026-09-04)

• Vendor the int2DDS FFI 0.1.4 release assets in place of 0.1.3. The C API is unchanged: the published int2dds-ffi.h differs only in added safety documentation, every declaration is identical. The libraries are a fresh build of int2DDS d600e70, so the sha256 of every artifact moved.
• The glibc floor is unchanged (2.28 on x86_64 and aarch64, 2.34 on armhf) and so is the soname, libint2dds_ffi.so.0.
• Contributors: Intellectus Corp.

0.1.3 (2026-09-02)

• Vendor the int2DDS FFI 0.1.3 release assets in place of 0.1.1. The published v0.1.3 tarball ships the same int2dds-ffi.h as its git tag, so the version string identifies the ABI again; the v0.1.1 assets had been rebuilt in place under one version and did not.
• Lower the glibc floor from 2.34 to 2.28 on x86_64 and aarch64, widening the set of hosts the prebuilt artifact runs on. armhf stays at 2.34 and the musl builds are unaffected.
• The soname is unchanged at libint2dds_ffi.so.0.
• Contributors: Intellectus Corp.

0.1.1 (2026-08-28)

• Move the package into the rmw_int2dds repository, next to rmw_int2dds_cpp, so the two are released in lockstep. The prebuilt FFI tarballs are still published on the int2dds_ffi_vendor release page and are downloaded and sha256-verified at CMake configure time, unchanged.
• Contributors: Intellectus Corp.