You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a feature that separates the abstraction from the basic interface
of the Rust-native crate. This feature is enabled by default so as not
to break existing uses.
Signed-off-by: Ionut Mihalcea <[email protected]>
Copy file name to clipboardExpand all lines: tss-esapi/README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,17 @@ time using the headers identified on the system.
17
17
18
18
Our end-goal is to achieve a fully Rust-native interface that offers strong safety and security guarantees. Check out our [documentation](https://docs.rs/tss-esapi/*/tss_esapi/#notes-on-code-safety) for an overview of our code safety approach.
19
19
20
+
## Cargo Features
21
+
22
+
The crate currently offers the following features:
23
+
24
+
*`generate_bindings` - forces the underlying `tss-esapi-sys`
25
+
crate to regenerate the FFI bindings on each build, using the TSS
26
+
libraries available on the build machine.
27
+
*`abstraction` (enabled by default) - provides a set of abstracted primitives
28
+
on top of the basic Rust-native ESAPI API provided by the crate. This feature
29
+
can be turned off to reduce the number of dependencies built.
30
+
20
31
## Cross compiling
21
32
22
33
For more information on cross-compiling the `tss-esapi` crate, please see the README of the `tss-esapi-sys` crate.
0 commit comments