[New Package] TypeDBDriverClib_jll v3.8.1

[FrankUrbach]

New JLL package: TypeDBDriverClib_jll

What

Adds a BinaryBuilder recipe for libtypedb_driver_clib, the C FFI layer of the
TypeDB Driver (TypeDB 3.x).

The library is implemented in Rust (c/ crate in the typedb-driver workspace)
and exposes a C-compatible API for use by language bindings.

Source

• Repository: https://github.com/typedb/typedb-driver
• Tag: 3.8.1 (commit 8e8d4a43da32adc1c56084f4d34174bebd0ce34a)

Platforms

• x86_64-linux-gnu
• aarch64-linux-gnu
• x86_64-apple-darwin
• aarch64-apple-darwin
• x86_64-w64-mingw32

Build

Uses compilers = [:c, :rust] and dont_dlopen = true. Builds the
typedb_driver_clib crate via cargo build -p typedb_driver_clib from the
workspace root. On Windows, Rust omits the lib prefix; the
LibraryProduct accepts both libtypedb_driver_clib and typedb_driver_clib.

v1 CI failure (fixed)

The first CI run failed because of three mistakes in the recipe:

• Directory was named T/TypeDBDriverClib_jll/ instead of T/TypeDBDriverClib/
• name included the _jll suffix (BinaryBuilder appends it automatically)
• Used ${CARGO_BUILD_TARGET} instead of the correct ${rust_target}

Consumer

Intended for use by
TypeDBClient_2.jl,
a Julia FFI client for TypeDB 3.x.

[FrankUrbach]

Pushed a fix for the CI failures.

Root cause: c/Cargo.toml in typedb/typedb-driver at tag 3.8.1 does not declare crate-type = ["cdylib"] under [lib]. The TypeDB project uses Bazel (rust_shared_library rule) as its actual build system for the C FFI library; the Cargo manifest is incomplete for shared-library builds.

Fix: Changed the build command from

cargo build --release -p typedb_driver_clib

to

cargo rustc --release -p typedb_driver_clib -- --crate-type=cdylib

This passes the crate type explicitly at compile time so cargo produces libtypedb_driver_clib.{dylib,so,dll} instead of a Rust static library (rlib).