Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 7639] Bluetooth minor enhancement

Date: Fri, 24 Aug 2012 09:26:10 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7639

--- Comment #26 from Michal Labedzki <michal.labedzki@xxxxxxxxx> 2012-08-24 09:26:09 PDT ---
(In reply to comment #25)
> Hi,

Hi. 

> 
> You really need only to rebuild libwireshark, so you can only do: make -C
> epan/,
> and you can test if your dissector really compiles with: make -C
> epan/dissectors packet-foo.o
> 
> Now put it as nice aliases in your .profile ;-)

So, I want to do it more automatically then manual. This was done in 1-2. I do
not want to hack Wireshark every time when I want to do some changes in
dissectors (many small changes and build them sequentially: change, compile,
check; change, compile, check...). This is very user-friendly (developer-only)
solution. Why do not provide to Wireshark one more helpful solution?

> 
> We could also improve building process with autotools.
> When building it generates few static archives (libdissectors.a,
> libdirtydissectors.a, ...) and later add them to libwireshark.so, 
> cmake AFAIK compiles all files directly to libwireshark.so

Linking .so in Wireshark should be slow too. Let me see... libdissectors.a = 50
MiB... big.

> Btw. I advocate that no-one really use all dissectors, and compiling all of
> them is waste of time and memory.

I am agree, but personally I like to have all dissectors in one Wireshark (and
many Wireshark instances). (even DBus packets over Bluetooth never happen :))

> Adding lot of options: --without-tcp, ---without-udp to configure sucks for me,


No, no... Please do not do that :)

> but please check:
>   http://www.wireshark.org/lists/wireshark-dev/201104/msg00316.html
> Kconfig support tristate logic (N/M/Y), so it should be doable to select what
> dissectors should be compiled as module (aka plugins).
> 
> Dunno how to integrate Kconfig with wireshark.

Nice idea.


I do not see any conflicts with Wireshark politics in patches 1-2, so I want to 
convince to integrate it. An please remember. These changes are minor, so does
not change anything important. Please do not think about "separation" like
"exclude". Thanks.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.