Am I correct in saying that in order to build a plugin for both win32 and win64
that I have to install the source twice and build each version. Then copy my
plugin into each source tree and build the two executables.
If so, then, with the recent discussions regarding moving to powershell and or
Thus wrote Gerald Combs (ger...@wireshark.org):
> On 1/5/12 3:19 AM, Sake Blok wrote:
> > Gerald,
> > Are plans to meet around FOSDEM finalized? For me it would be possible to
> > meet up during the day on Friday 3rd (after which we could join the FOSDEM
> > Beer Event :-)). I could either driv
Hello i am having the same bug related here:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5696
Is this issue solved ?
"
2) The protocol payload length is not set correctly. Our hardware also captures
the Ethernet CRC32, which is incorrectly assumed to be part of the protocol
payload (sta
On Sat, Jan 14, 2012 at 07:31:16AM -0800, buildbot-no-re...@wireshark.org wrote:
> The Buildbot has detected a new failure on builder
> Visual-Studio-Code-Analysis while building Wireshark (development).
> Full details are available at:
>
> http://buildbot.wireshark.org/trunk/builders/Visual-Stu
On Thu, Jan 05, 2012 at 08:03:26PM -0500, Ed Beroset wrote:
> Joerg Mayer wrote:
>
>> I have a few small questions that came up during looking at the patch
>> (not all of them relevant to this patch!):
>> - why is eax.[ch] in epan instead of epan/crypt/?
>> - why do we have files named crypt/crypt-
> What are the warnings in packet-gsm_a_common.c and packet-x11.c?
Looks like my reply got stuck in moderation due to size.
So here is the (incomplete) short version:
jmayer@egg:/tmp/qt/epan> make dissectors/packet-gsm_a_common.c.o
Building C object epan/CMakeFiles/epan.dir/dissectors/packet-gsm
