[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-dev
Subject:    Re: [Wireshark-dev] Compiling your dissector, quickly?
From:       Jeff Morriss <jeff.morriss.ws () gmail ! com>
Date:       2011-02-14 15:42:55
Message-ID: 4D594D7F.702 () gmail ! com
[Download RAW message or body]

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 wireshark
> 
> In 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


[prev in list] [next in list] [prev in thread] [next in thread]