Crate ritual_build

Implementation of ritual's build script. Default generated build script uses this crate as a build dependency and just calls ritual_build::run(). If a custom build script is used, it should either use the same call to execute all operations normally or use Config type to change the build script's settings.

See README of the repository root for more information.

Crates generated by ritual require multiple custom build operations:

• Apply extra build configuration passed via environment variables (RITUAL_LIBRARY_PATH, RITUAL_FRAMEWORK_PATH, RITUAL_INCLUDE_PATH);
• Select active build configuration based on current target;
• Build the C++ wrapper library;
• Generate ffi.rs file with actual linking attributes;
• Determine sizes of C++ types with stack allocation place;
• Print cargo attributes required for linking the crate. It appears a common task to perform other custom operations in the build script, so all the above operations are implemented as a separate crate which is used as build dependency of the default generated build script. If a custom build script is defined, it should use this crate's API to perform the necessary build operations.

Re-exports

pub use ritual_common as common;

Structs

Config

Configuration of the build script.

Functions

run	Runs the build script with default configuration. See Config::run for more information.
try_run	Same as run(), but result of the operation is returned to the caller.