Wireshark mailing list archives
Re: Compiling your dissector, quickly?
From: Jeff Morriss <jeff.morriss.ws () gmail com>
Date: Mon, 14 Feb 2011 10:42:55 -0500
In fact the "&& make wireshark" part is not necessary when compiling in epan (unless you're building a static libwireshark). It IS necessary when compiling in gtk since the result of that compile is a static library that has to be (re)linked into the wireshark executable.
Jaap Keuter wrote:
I'm not sure what environment your working in but here's what you can try: make -C epan && make wiresharkIn the top directory.Thanks, Jaap On 12 feb. 2011, at 10:52, "Ivan R. Sy" <ivan_jr () yahoo com> wrote:Hi! hello, its been a while since I did some tweaks with dissectors. Unfortunately for me, im doing some devs on a VM. Question is, when I modify a dissector file (for example, epan/dissector/packet-proto.c) what is the quickest way for me to re-compile my wireshark so I can test it? currently, im doing 'gmake' on the top directory of wireshark... and it takes a while. I've tried to just do 'gmake', inside epan/dissectors.... but its not reflecting my adjustments. thanks!
___________________________________________________________________________ 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
Current thread:
- Compiling your dissector, quickly? Ivan R. Sy (Feb 12)
- Re: Compiling your dissector, quickly? Jaap Keuter (Feb 12)
- Re: Compiling your dissector, quickly? Jeff Morriss (Feb 14)
- Re: Compiling your dissector, quickly? Jaap Keuter (Feb 12)