记录技术和生活 Zola 2026-10-15T09:00:00+08:00 https://blog.laofu.online/tags/abi/atom.xml 2026-10-15T09:00:00+08:00 2026-10-15T09:00:00+08:00 bigfish https://blog.laofu.online/blog/20261015-0900-rpicha-jian-abijia-zai-ji-zhi/

<p>很多人第一次看到 rpi 的 Rust 插件，会把它理解成“编译出一个动态库，然后让 rpi 找到它”。这句话方向没错，但省略了最关键的部分：动态库如何证明自己是一个 rpi 插件？注册的工具如何跨过 Rust 边界？一次调用结束后，插件里的内存由谁释放？源码目录里的 crate 又是怎样变成项目里的 package 的？</p> <p>这篇文章从 <code>examples/plugin-stub</code> 这样的最小 demo 开始，沿着 <code>rpi-plugin-sdk</code>、<code>rpi-extensions</code> 和 <code>rpi-cli</code> 的实现，解释这条链路：</p> <pre class="giallo z-l-code z-d-code" ><code data-lang="mermaid"><span class="giallo-l"><span class="z-l-13 z-d-8">flowchart</span><span class="z-l-9 z-d-6"> LR</span></span> <span class="giallo-l"><span class="z-l-3 z-d-10"> A</span><span class="z-l-13 z-d-8">[</span><span class="z-l-12 z-d-5">插件源码\nRust crate</span><span class="z-l-13 z-d-8">]</span><span class="z-l-13 z-d-8"> --&gt;</span><span class="z-l-3 z-d-10"> B</span><span class="z-l-13 z-d-8">[</span><span class="z-l-12 z-d-5">cdylib\n.dll / .so / .dylib</span><span class="z-l-13 z-d-8">]</span></span> <span class="giallo-l"><span class="z-l-3 z-d-10"> B </span><span class="z-l-13 z-d-8">--&gt;</span><span class="z-l-3 z-d-10"> C</span><span class="z-l-13 z-d-8">[</span><span class="z-l-12 z-d-5">rpi 加载器\nlibloading</span><span class="z-l-13 z-d-8">]</span></span> <span class="giallo-l"><span class="z-l-3 z-d-10"> C </span><span class="z-l-13 z-d-8">--&gt;</span><span class="z-l-3 z-d-10"> D</span><span class="z-l-13 z-d-8">[</span><span class="z-l-12 z-d-5">rpi_plugin_register</span><span class="z-l-13 z-d-8">]</span></span> <span class="giallo-l"><span class="z-l-3 z-d-10"> D </span><span class="z-l-13 z-d-8">--&gt;</span><span class="z-l-3 z-d-10"> E</span><span class="z-l-13 z-d-8">[</span><span class="z-l-12 z-d-5">HostApi + ExtensionRegistry</span><span class="z-l-13 z-d-8">]</span></span> <span class="giallo-l"><span class="z-l-3 z-d-10"> E </span><span class="z-l-13 z-d-8">--&gt;</span><span class="z-l-3 z-d-10"> F</span><span class="z-l-13 z-d-8">[</span><span class="z-l-12 z-d-5">RegistrySnapshot</span><span class="z-l-13 z-d-8">]</span></span> <span class="giallo-l"><span class="z-l-3 z-d-10"> F </span><span class="z-l-13 z-d-8">--&gt;</span><span class="z-l-3 z-d-10"> G</span><span class="z-l-13 z-d-8">[</span><span class="z-l-12 z-d-5">Agent 会话中的工具\n事件与其他扩展能力</span><span class="z-l-13 z-d-8">]</span></span></code></pre> <p>这里的“插件”指 rpi 的 Rust 原生 ABI 扩展，不是 MCP Server，也不是一个通过 HTTP 或 stdio 运行的外部进程。它和宿主运行在同一个进程里，因此能力强、开销低，但也意味着插件是本机可信代码，ABI、内存所有权和生命周期必须非常明确。</p> <p>本文讨论的是 rpi 的原生 ABI 插件机制。由于 ABI、loader 和 package 命令会随仓库版本变化，下面的文件名、符号名和命令都应与所读源码版本一起核对；代码块中明确标注为“示意”的部分，不等于可直接复制运行的最小插件。文章关注一条主线：插件如何从动态库进入注册表，再被会话驱动；不把它扩展成完整的 Rust FFI 教程。</p>