Wireshark mailing list archives
Linking library static when developing plugin dissector
From: Marcus Wallstersson <wallstersson () gmail com>
Date: Mon, 7 May 2012 10:12:03 +0200
Hello! I'm developing a plugin dissector on Ubuntu following the README.developer and README.plugin I used the gryphon plugin as "template" as the guide recommended. The plugin includes a parser ie. "#include <myparser.h>". The library files for this parser is /usr/lib64/libmyparser.so and /usr/lib64/libmyparser.a It works great on my computer with the library files. But my problem is that I need to link this library static into the .libs/myplugin.so so that a person that don't have the library files can run the plugin. I ran the command "nm .libs/myplugin.so" and it shows that the parser functions are Undefined "U" I did two static link tests on a small c application using my parser, and it worked great on another computer. "gcc test.c /usr/lib64/libmyparser.a" "gcc test.c -Wl,-Bstatic -lmyparser -Wl,-Bdynamic" How should i do this linking when building my plugin? Regards Marcus Wallstersson ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Linking library static when developing plugin dissector Marcus Wallstersson (May 07)