Extensions
An extension packages modules such as plugins and scripts. The upstream Project window exposes File → Install Extensions; installation and removal take effect after restarting the application. A plugin may then need to be enabled in a tool’s configuration.
Install deliberately
Section titled “Install deliberately”- Check the extension’s publisher, source, license, and release notes.
- Confirm the exact application version it was built against.
- Back up important projects before testing it.
- Use the installation dialog with the extension archive.
- Restart and verify its expected action or plugin.
- Check the application log if loading fails.
Upstream identifies extension metadata through extension.properties. A version mismatch is highlighted in the dialog. Do not treat a successful unzip as proof of binary or API compatibility.
Build an extension
Section titled “Build an extension”The release’s GhidraBuild/Skeleton material and installed extension build support are the starting points. Build against a fully built installation and pin that version in CI. VERIFY Opcodex artifact paths and version identity before publishing an extension; branding changes do not guarantee compatibility with arbitrary upstream builds.
Community must not depend on Pro modules. The six planned Pro extensions will have their own compatible builds and documentation when released. See Community vs Pro for scope.
TODO: update screenshot of the Opcodex extension installation dialog. VERIFY the final menu label and plugin activation flow.
Sources: Extension Installation help, GhidraBuild/Skeleton.
Adapted from the Ghidra documentation (Apache 2.0).