jxoesneon-tectonic-bridge_icu

Crates.iojxoesneon-tectonic-bridge_icu
lib.rsjxoesneon-tectonic-bridge_icu
version0.17.3
created_at2026-01-04 21:05:34.69585+00
updated_at2026-01-12 09:00:42.526255+00
descriptionInternal crate for the Tectonic project: tectonic_bridge_icu
homepagehttps://tectonic-typesetting.github.io/
repositoryhttps://github.com/tectonic-typesetting/tectonic/
max_upload_size
id2022470
size7,569
(jxoesneon)

documentation

https://docs.rs/tectonic_bridge_icu

README

The tectonic_bridge_icu crate

[!NOTE] This crate is part of the FerroTeX project, a specialized fork of Tectonic. It is published to crates.io as jxoesneon-tectonic-bridge_icu.

This crate is part of the Tectonic project. It exposes the C API of the ICU4C Unicode library the Rust/Cargo build framework, with no Rust bindings.

There are a variety of other low-level ICU-related crates available, with rust_icu perhaps taking the most systematic approach. This package is distinctive because:

  • It uses Tectonic’s dependency-finding framework, which supports both pkg-config and vcpkg.
  • It ensures the ICU C API is exposed to Cargo.
  • Because it does not need to provide Rust bindings, it avoids a good deal of grief relating to bindgen, symbol versioning, etc.

Ideally, though, one day this crate will be superseded by a true Rust "sys crate".

If your project depends on this crate, Cargo will export for your build script an environment variable named DEP_ICUUC_INCLUDE_PATH, which will be a semicolon-separated list of C include directories enabling your code to include the unicode/* headers.

You will need to ensure that your Rust code actually references this crate in order for the linker to include linked libraries. A use statement will suffice:

#[allow(unused_imports)]
#[allow(clippy::single_component_path_imports)]
use tectonic_bridge_icu;

Cargo features

At the moment this crate does not provide any Cargo features.

Commit count: 4078

cargo fmt