https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7639
--- Comment #29 from Michal Labedzki <michal.labedzki@xxxxxxxxx> 2012-08-24 13:14:31 PDT ---
(In reply to comment #27)
> I think it'd doubtful that we'd make the bluetouth dissector a plugin,
> if you want to make progress it's much more likly to happen with patches
> to the current structure. Just my 2 cents.
Bluetooth plugin is not part of Wireshark release. Why do not to help developer
in his job? Otherwise ther is no sens to have plugin subsystem and it should be
removed.
Example:
Wireshark + RFCOMM dissector + Bluetooth plugins within RFCOMM that override
internal RFCOMM --> there is no need to spend a lot of time to rebuild full
Wireshark, while there is only change in RFCOMM dissector. Than there is no any
work to do for applying patch to internal tree, because it is already there.
Makefile Magic.
So, is there any change to put it intro the source or everyone should do the
same privately? (I guess no one interesting in rebuild whole Wireshark while
can rebuild only specified plugin to test something)
Maybe I miss something. How to create completely new dissector? I do that by
creating plugin and working on it, than try to integrate it statically into
Wireshark (by this bugzilla)
>From Wireshark docs
(http://www.wireshark.org/docs/wsdg_html_chunked/ChDissectAdd.html#id36146471):
> 9.2.1. Setting up the dissector
>
> The first decision you need to make is if this dissector will be a built-in dissector, included in the main program, or a plugin.
>
> Plugins are the easiest to write initially, so let's start with that. With a little care, the plugin can be made to run as a built-in easily too - so we haven't lost anything.
My only intention is faster fixing dissector to do them as temporary plugin.
There is already something like it in Wireshark, check "QtShark.pro"
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.