wireshark-dev October 2010 archive
Main Archive Page > Month Archives  > wireshark-dev archives
wireshark-dev: [Wireshark-dev] Bug #5292: MacOSX and linking

[Wireshark-dev] Bug #5292: MacOSX and linking

From: Babikyan, Armen - 0663 - MITLL <armenb_at_nospam>
Date: Tue Oct 12 2010 - 19:09:35 GMT
To: "wireshark-dev@wireshark.org" <wireshark-dev@wireshark.org>

  Hi,

I think I jumped the gun and filed bug report #5292 without completely
understanding what's going on. I have some questions:

On MacOSX, it seems that the libraries that are included with the
Wireshark.dmg installer from wireshark.org are not properly linked.
When running otool -L on them (e.g. libwireshark.dylib), the library
thinks it's "id" (the second line in the output) is
/usr/local/lib/libwireshark.dylib rather than
/Applications/Wireshark.app/Contents/Resources/lib/libwireshark.dylib.
If libwireshark.dylib is not being dlopen()'ed, how is
Contents/MacOS/Wireshark being able to load libwireshark.dylib without
encountering an error? Is there an implicit environment variable being
set somewhere? I am relatively new at developing for MacOSX.

You may be question the reason for why I am interested in this. I
developed a GPLv2 tool for Linux that allows Wireshark's packet
dissection engine to be used in high-level interpreted programming
languages (Python and Matlab in particular) to extract vectors of packet
information for subsequent post-processing and analysis. I have ported
the tool to MacOSX, but since I link with libwireshark, libwiretap,
libwsutil directly, I'd rather link with existing copies of the library
on my installation target rather than distribute Wireshark libraries
with my tool. With respect to the above problem, I was unable to load
Wireshark.app's libraries unless I ran "install_name_tool -id" and
"install_name_tool -change" on each library that comes with Wireshark.app.

Any insight is greatly appreciated. Thanks!

Armen

-- Armen Babikyan MIT Lincoln Laboratory armenb@ll.mit.edu . 781-981-1796 ___________________________________________________________________________ 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