Files
loot-condition-interpreter/README.md
T

74 lines
2.2 KiB
Markdown
Raw Normal View History

loot-condition-interpreter
==========================
2020-07-12 10:27:33 +01:00
![CI](https://github.com/loot/loot-condition-interpreter/workflows/CI/badge.svg?branch=master)
2022-11-09 00:09:35 +00:00
[![Coverage Status](https://coveralls.io/repos/github/loot/loot-condition-interpreter/badge.svg?branch=master)](https://coveralls.io/github/loot/loot-condition-interpreter?branch=master)
2018-11-06 14:13:37 +00:00
A library for parsing and evaluating LOOT's metadata condition strings. It
provides:
2020-07-12 08:54:38 +01:00
- Support for metadata syntax v0.15 condition strings.
2018-11-06 14:13:37 +00:00
- Condition string parsing without evaluation, for checking syntax.
- Evaluation of parsed condition strings.
2019-06-16 20:36:14 +01:00
- Efficient and safe concurrent condition evaluation thanks to Rust's safety
2018-11-06 14:13:37 +00:00
guarantees.
- Caching of individual function evaluation results and calculated CRCs.
- Executable version parsing without any external runtime dependencies.
- Lots of tests, and benchmarks.
- A C FFI library that wraps the Rust library.
2018-10-06 16:00:47 +01:00
2018-11-06 14:13:37 +00:00
## Build
Make sure you have [Rust](https://www.rust-lang.org/) installed.
To build the Rust and C FFI libraries, run:
```
cargo build --release --package loot-condition-interpreter-ffi
```
To generate a C++ header file as part of the build, instead run:
```
cargo build --release --package loot-condition-interpreter-ffi --all-features
```
This will create a file at `ffi/include/loot_condition_interpreter.h`.
2018-11-06 14:13:37 +00:00
However, this involves building [cbindgen](https://github.com/eqrion/cbindgen)
as a dependency, which is relatively slow. If you have cbindgen installed
separately, it's faster to generate the headers using its CLI:
```
cbindgen ffi/ -o ffi/include/loot_condition_interpreter.h
2018-11-06 14:13:37 +00:00
```
## Tests & Benchmarks
The tests and benchmarks need the [testing-plugins](https://github.com/WrinklyNinja/testing-plugins)
and the [LOOT API v0.13.8](https://github.com/loot/loot-api/releases/tag/0.13.8)
2020-07-12 10:27:33 +01:00
Windows archives to be extracted and present in the repo root. See the GitHub
Actions CI workflow for examples on what should be extracted where.
2018-11-06 14:13:37 +00:00
To run the Rust tests:
```
cargo test --all
```
To run the benchmarks:
```
cargo bench
```
There are also C++ tests for the FFI library, they require a C++ toolchain and
[CMake](https://cmake.org/) to be installed. To run the C++ tests:
```
mkdir ffi/build
cd ffi/build
cmake ..
cmake --build .
ctest
```