Publishing binaries for a new plugin

[Raúl Kripalani <raul.kripalani () consensys net>]

Hello,

We’ve built a Wireshark dissector plugin for Ethereum devp2p protocols, and
we’re preparing it to publish it on Github shortly. We want to offer
precompiled .so and .dll downloads, so that users can place them in their
plugins directory for an easy start.

I’m running on Mac OS X 10.13.4, and using a Ninja build against
master-2.6. It generates the application binary properly (Wireshark.app)
and places the plugin .so under the bundled
Contents/PlugIns/wireshark/2.6/epan directory of the bundle.

However, if I extract the file manually and place it inside the
Wireshark.app package of a downloaded version (2.6.1) (simulating what a
user would do), the plugin gets recognised in the About > Plugins pane, but
there are no signs of the dissector, nor the menu points for the SRT table,
statistics table, etc. anywhere in the UI.

If I replace the .so of other plugins like ethercat, gryphon, etc. in
downloaded distribution with the ones generated from my build, the same
thing happens.

May someone point me to what might be happening here?

Thank you,
Raúl.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe