diff options
| author | Glenn Smith <glenn@vector35.com> | 2024-06-25 14:36:20 -0400 |
|---|---|---|
| committer | Glenn Smith <glenn@vector35.com> | 2024-06-25 14:36:20 -0400 |
| commit | 9985498549204743944246577439929357952788 (patch) | |
| tree | fd2c4873040b7fa9b6d080b3cd4cbb1027f58a97 /docs/dev/plugins.md | |
| parent | 1ffd063fc7e0bad3ee60f257d0df2324fbe09a36 (diff) | |
Fix url to sample plugin in plugins.md
Diffstat (limited to 'docs/dev/plugins.md')
| -rw-r--r-- | docs/dev/plugins.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/plugins.md b/docs/dev/plugins.md index 53a1dd87..2f0fc72c 100644 --- a/docs/dev/plugins.md +++ b/docs/dev/plugins.md @@ -207,7 +207,7 @@ class, and you should only ever handle Refs or bare pointers. When in doubt, fee ### Automated GitHub CI Managing build infrastructure to build cross-platform native plugins can be a headache even for stables, let alone -trying to track all dev releases. To help with that, we've published an [example plugin](https://github.com/CouleeApps/binja-ci-tests) that includes GitHub +trying to track all dev releases. To help with that, we've published an [example plugin](https://github.com/Vector35/sample_plugin_cpp) that includes GitHub actions to build on MacOS, Linux, and Windows. Combining this with something like a [plugin loader](https://github.com/rikodot/binja_native_sigscan_loader) can simplify both publishing and using native plugins. |