https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7639
--- Comment #25 from Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx> 2012-08-23 05:19:55 PDT ---
Hi,
> try "make bluetooth-plugins" to see how speed building dissectors can be (and
> of course "touch" one of Bluetooth dissectors). On the other hand if you know
> better way to do that please provide me solution.
1. Build in tmpfs/ramfs mounted directory
2. Don't use gcc, but some faster compiler, clang? TCC?
3. Set CFLAGS="-O0 -pipe"
(In reply to comment #12)
> because you can rebuild dissectors in "realtime", so no 20-30 seconds (and cry if compilation error, so 1 minutes for nothing...), than 0-2 seconds - 2 seconds
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 ;-)
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
Patches welcome.
Btw. I advocate that no-one really use all dissectors, and compiling all of
them is waste of time and memory.
Adding lot of options: --without-tcp, ---without-udp to configure sucks for me,
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.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
