This happens when you compile the plugin in an environment that does not match the gateway compilation environment exactly. To get around this you have two options.
- Build the gateway yourself, and then use the same environment to build your plugins, you will not be able to use any of our official packaged gateways, however you will have a singular environment to compile gateways and plugins going forward.
2.Use our plugin compiler offered in a container (I would recommend this over the first option) It is designed to compile plugins, and it contains the exact environment the packaged gateway is built in, therefore able to build a plugin binary that will load into our packaged gateways.
Documentation on compiling plugins using the plugin compiler is available on our documentation website, in fact the whole golang plugin section has been rewritten recently with more examples and information relating to the 3.2.x method of compiling plugins. Please take another look if you haven’t done so recently.
Hope that helps!