tinyxml2-usage

tinyxml2-usage

A consumer example for the cabin-ports/tinyxml2 registry package, published from the curated ports/tinyxml2/11.0.0/ package directory. The program links against tinyxml2 (a C++ library), parses a small XML document, and prints an element's text plus the compiled-in tinyxml2 version.

This is not itself a port and does not vendor or copy tinyxml2 sources. It demonstrates depending on a published C++ registry package from a normal Cabin package. The first cabin build resolves "cabin-ports/tinyxml2" = "=11.0.0" against the registry index, downloads the published package archive, verifies its checksum, extracts it under Cabin's cache, and then builds normally; subsequent builds reuse the cache.

Build and run

cd examples/tinyxml2-usage
cabin build
cabin run

Expected output (the version is whatever the resolved package pins):

tinyxml2 parsed to: Cabin
tinyxml2 version: 11.0.0

Offline

Registry dependencies resolve through the hosted registry by default; verified packages download without an account or token - cabin login is only needed to publish (see docs/remote-registry.md). Once the package is cached, later builds reuse the downloaded archive without re-fetching it. Resolving still consults the registry index, so a fully offline build needs a local index; see docs/vendoring-offline.md for the cabin vendor + --offline --index-path workflow.

The integration test for this example (crates/cabin/tests/cabin_examples.rs::tinyxml2_usage_builds_and_runs) runs only with --ignored and needs outbound network: it stages the committed ports into a local file registry through the publisher pipeline and builds against that with --index-path, downloading the pinned upstream archives on the way.