CAI SDK C++ library

The c2pa-c repository implements C++ APIs that:

• Read and validate C2PA data from media files in supported formats.
• Add signed manifests to media files in supported formats.

Although this library works for plain C applications, the documentation assumes you're using C++, since that's most common for modern applications.

For the best experience, read the docs on the CAI Open Source SDK documentation website.

If you want to view the documentation in GitHub, see:

• Using the C++ library
• Supported formats
• Configuring the SDK using Context and Settings.
• Using working stores and archives.
• Using Builder and Reader together to selectively construct a manifest by filtering actions and ingredients.
• Release notes

Using c2pa_cpp

The recommended way to use this library in your own CMake project is with FetchContent:

include(FetchContent)

FetchContent_Declare(
    c2pa_cpp
    GIT_REPOSITORY https://github.com/contentauth/c2pa-c.git
    GIT_TAG main  # Or use a specific release tag
)
FetchContent_MakeAvailable(c2pa_cpp)

add_executable(myapp main.cpp)
target_link_libraries(myapp PRIVATE c2pa_cpp)

This will automatically fetch, build, and link the c2pa_cpp library and its dependencies.

Note: This project uses pre-built dynamic libraries from the c2pa-rs repository. It should select the correct library for your platform. If your platform is not supported, you can build your own library using the c2pa_rs repo.

Example usage

See the examples/ directory for sample applications that demonstrate how to use the library in practice.

Development

This project has been tested on macOS and should also work on common Linux distributions.

You must install the Ninja build system to run the unit tests.

Building using pre-built C FFI libraries

Building the library holding the C++ SDK requires GNU make, which is installed on most macOS systems.

Enter this command to build the SDK:

make release

This will download the pre-build libraries published with c2pa releases, build and link the C++ code.

The Makefile has a number of other targets; for example:

• test to run unit tests
• examples to build and run the C++ examples.
• all to build and run everything.

Results are saved in the build directory.

Building using local sources

This project can also be built entirely from source (without pre-built library download), with the pre-requisite that you will also need c2pa-rs on the local machine, as well as the Rust toolchain.

To build in this case, the build scripts need to be able to locate the c2pa-rs sources as well as the library this builds for linking. This is done by setting environment variables in the terminal where the builds will run.

# Enable local c2pa-rs build
export C2PA_BUILD_FROM_SOURCE=ON

# If local build is enabled, set this environment variable to contain the path to c2pa-rs sources
export C2PA_RS_PATH=path_to_c2pa_rs_sources

# Since this is going to build Rust code, the build system needs to locate cargo, the tool to build Rust code
# Add Rust cargo to PATH if not already there
export PATH="$HOME/.cargo/bin:$PATH"

# macOs: Set built library path for running tests
export DYLD_LIBRARY_PATH="$(pwd)/build/release/tests:$DYLD_LIBRARY_PATH"

# Linux: Set built library path for running tests
export LD_LIBRARY_PATH="$(pwd)/build/release/tests:$LD_LIBRARY_PATH"

Testing

Build the unit tests by entering this make command:

make test

Building API documentation

API documentation generated by Doxygen is automatically built on each PR.

To generate API docs locally, these are the main files:

• Configuration file: c2pa-c/Doxyfile
• Script: c2pa-c/scripts/generate_api_docs.sh
• Output directory: docs/_build/html

Install Doxygen if needed:

macOS: brew install doxygen
Ubuntu/Debian: sudo apt-get install doxygen

To generate docs, enter the command:

./scripts/generate_api_docs.sh

Or run make -C docs.

Open _build/html/index.html to see the results.

License

This package is distributed under the terms of both the MIT license and the Apache License (Version 2.0).

Note that some components and dependent crates are licensed under different terms; please check the license terms for each crate and component for details.

Contributions and feedback

We welcome contributions to this project. For information on contributing, providing feedback, and about ongoing work, see Contributing.