philss/Rustler Precompiled Action

Precompiles Rustler projects and outputs files in the expected filenames.

Trust Signals

name	description	required	default
project-name	Name of the crate that is being built. This is the same of the Cargo.toml of the crate.	yes	—
project-version	The version to use in the name of the lib. This mostly matches the Elixir package version.	yes	—
cross-version	The version desired for cross, the tool that builds for multiple plataforms. It's possible to specify a version, or the string "from-source" to install from the main branch of the project repository.	no	v0.2.4
use-cross	If the target requires the usage of cross.	no	false
target	The Rust target we are building to.	yes	—
nif-version	The NIF version that we are aiming to.	no	2.16
project-dir	A relative path where the project is located. The script is going to enter this path in order to compile the NIF. For example, "native/my_nif".	yes	./
variant	An alternative version for a given target that is useful when you are building for the same target, but with different dependencies, or hardware capatibilities. This name should be a valid string that can be represented as an Elixir atom. Prefer to use only alphanumerics and underscores. This is going to be appended to the artifact name.	no	""
cargo-args	A string with additional arguments to be appended to the build command. This is useful to pass flags like `--features`. Notice that the flags `--release` and `--target` are going to be passed down automatically. The flag `--features` may be passed, depending of the NIF version. But you can always pass this flag multiple times.	no	""

name	description
file-name	The tarball compressed file name that was generated.
file-path	The file path of the tar.gz generated. For compatible reasons, this is equal to the file name. The final file is going to be placed at the root of your project.
file-sha256	The SHA256 of the tarball file.