Which version of Wireshark are you compiling against? With
1.2.8, my plugins get copied automatically. I haven’t integrated them with the
trunk yet. Anyway, I think you probably just need to edit plugins/Makefile.nmake,
possibly as easy as adding your plugin to the PLUGIN_LIST, which
the latest README.plugins mentions, or if you’re using an older
version such as 1.2.8 like I am, then adding the appropriate xcopy command
to the install-plugins target. As for the autogen.sh problem, first, why sudo? If
still experiencing problems without using sudo, then you might try
adding “set –x” to the top of the script after the comment block for
additional debug information, which might help isolate the problem. The
versions of the tools should be OK. According to the trunk’s autogen.sh, autoconf must
be >= 2.60, automake >= 1.9 and libtool >= 1.4. - Chris From:
wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of ajay seshadri Thanks a lot Chris.
From: "Maynard, Chris"
<Christopher.Maynard@xxxxxxxxx> 1. export
WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 2. “./configure
--prefix=${HOME}/build/root”: That’s an example
of what you type on the command-line during the configure step. As far as I know, everything
in the README.plugins is accurate and applicable. BTW, on Windows, you don’t
have to copy any plugin .dll’s anywhere. Just run wireshark.exe from the wireshark-gtk2\
directory. - Chris From:
wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of ajay seshadri Hi Chris,
From: "Maynard, Chris"
<Christopher.Maynard@xxxxxxxxx> Have you read doc/README.plugins? - Chris From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of ajay seshadri Hi, What are the
changes to be made to compile and run a Wireshark dissector plugin in Linux?
The developer's manual gives in depth information about the changes to be made
to the various files (including *.nmake) to compile it in windows. Is 'make all'
sufficient in linux? Would it generate a *.so file? I would appreciate it if
anyone could guide me in this regard. Thanks, Ajay CONFIDENTIALITY NOTICE: The contents of this email are confidential and for the exclusive use of the intended recipient. If you receive this email in error, please delete it from your system immediately and notify us either by email, telephone or fax. You should not copy, forward, or otherwise disclose the content of the email. CONFIDENTIALITY NOTICE: The contents of this email are confidential CONFIDENTIALITY NOTICE: The contents of this email are confidential and for the exclusive use of the intended recipient. If you receive this email in error, please delete it from your system immediately and notify us either by email, telephone or fax. You should not copy, forward, or otherwise disclose the content of the email. |
- References:
- Re: [Wireshark-dev] building wireshark in linux
- From: ajay seshadri
- Re: [Wireshark-dev] building wireshark in linux
- Prev by Date: Re: [Wireshark-dev] building wireshark in linux
- Next by Date: [Wireshark-dev] UI for packets differing by a checksum on the end
- Previous by thread: Re: [Wireshark-dev] building wireshark in linux
- Next by thread: [Wireshark-dev] Crash In Wireshark Package
- Index(es):