From 8d158a62728cfabba4ac7b93cf89e55bcf130aa2 Mon Sep 17 00:00:00 2001 From: Grzegorz Nosek Date: Mon, 14 Oct 2024 06:41:27 +0200 Subject: [PATCH] update(docs): prefer crate_type=cdylib This makes for smaller binaries and not exporting every single symbol under the sun. Signed-off-by: Grzegorz Nosek --- falco_plugin/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/falco_plugin/README.md b/falco_plugin/README.md index a1bf1118..f5a565fa 100644 --- a/falco_plugin/README.md +++ b/falco_plugin/README.md @@ -14,7 +14,7 @@ capabilities. The typical way to distribute a Falco plugin is to build a shared library. To build a plugin as a shared library, you need to: -1. Specify `crate_type = ["dylib"]` in the `[lib]` section of `Cargo.toml`, +1. Specify `crate_type = ["cdylib"]` in the `[lib]` section of `Cargo.toml`, 2. Invoke [`plugin!`] and all the macros corresponding to the capabilities your plugin implements. The most basic `Cargo.toml` file for a dynamically linked plugin without any dependencies could be: @@ -26,7 +26,7 @@ version = "0.1.0" edition = "2021" [lib] -crate-type = ["dylib"] +crate-type = ["cdylib"] [dependencies] falco_plugin = "0.3.0"