On 1/6/12 3:15 PM, Roland Knall wrote:
On another note. If in the long term Qt is the way to go, should all
references to gtk usage be replaced by a more generic version of such
functions, which in the meantime call the gtk version as a first step?
That would allow for the future to prepare a
Balint Reczey balint.rec...@ericsson.com
wrote in news:4f0ed7c6.2030...@ericsson.com:
I have updated the ABI compatibility report here:
http://rbalint.cs.bme.hu/ws-ABI-1.6.4-1.6.5/
Interesting report.
The version numbers in the report are 1.1.0 and 1.1.1, what looks a bit
strange. But the
On Jan 8, 2012, at 12:08 PM, Balint Reczey wrote:
I have run tools/git-compare-abis.sh on latest master-1.6
(wireshark-1.6.4-21-ga6c3642).
The ABI is almost totally stable [1], which is very good sign for plugin
developers and for anyone using Wireshark's libraries. :-)
There is only
On Jan 13, 2012, at 7:59 AM, Harper wrote:
Balint Reczey balint.rec...@ericsson.com
wrote in news:4f0ed7c6.2030...@ericsson.com:
I have updated the ABI compatibility report here:
http://rbalint.cs.bme.hu/ws-ABI-1.6.4-1.6.5/
Interesting report.
The version numbers in the report are
On Jan 13, 2012, at 2:06 AM, Andreas Sikkema wrote:
Since getting back into Wireshark development I have this itch somewhere
int he back of my head to create a proper OS X version of Wireshark, but
have shied away from the amount of work involved ;-)
A Qt version would probably be good
That's what the commit message was about: They do create warnings. Please
move them back.
thanks
Joerg
On Fri, Jan 13, 2012 at 08:06:50PM +, g...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=40479
User: guy
Date: 2012/01/13 12:06 PM
Log:
On Jan 13, 2012, at 1:10 PM, Joerg Mayer wrote:
That's what the commit message was about: They do create warnings.
In which builds?
If causing warnings in *any* build is sufficient to flag them as dirty, there
are a *lot* of dissectors that need to be moved:
On Fri, Jan 13, 2012 at 01:23:09PM -0800, Guy Harris wrote:
On Jan 13, 2012, at 1:10 PM, Joerg Mayer wrote:
That's what the commit message was about: They do create warnings.
In which builds?
If causing warnings in *any* build is sufficient to flag them as dirty, there
are a *lot*
They have been causing warnings probably since I updated from opensuse 11.3 to
12.1 (gcc-4.6).
And finally, the build is finished:
/usr/bin/cmake -E cmake_progress_report /tmp/qt/CMakeFiles
[ 5%] Building C object
epan/CMakeFiles/epan.dir/dissectors/packet-dcerpc-dfs.c.o
cd /tmp/qt/epan
On Jan 13, 2012, at 1:31 PM, Joerg Mayer wrote:
They have been causing warnings probably since I updated from opensuse 11.3 to
12.1 (gcc-4.6).
So what are the warnings? We need to fix them so that the dissectors can be
treated as clean again. (This applies to all the dissectors temporarily
On Jan 13, 2012, at 1:47 PM, Joerg Mayer wrote:
And finally, the build is finished:
/usr/bin/cmake -E cmake_progress_report /tmp/qt/CMakeFiles
[ 5%] Building C object
epan/CMakeFiles/epan.dir/dissectors/packet-dcerpc-dfs.c.o
cd /tmp/qt/epan /usr/bin/gcc -Depan_EXPORTS -DHAVE_CONFIG_H
Hi Graham,
Oh, this is very actual issue.
My personal wishlist consist of two things:
1. Generation of register.c must be completely reworked, cause most times I
must wait about 15-20 minutes when recompiling sources;
2. Make CMake default for win-platform building is really good idea.
On Fri,
Hello List,
some while ago I sent a proposal to this list to enable filtering on
IP-addresses in arp requests. Guy asked whether generalizing that would
make more sense. IMO, it does. So, as a prove of concept I tried to
make everything of type FT_IPv4 filterable - and failed. My problem
is, that
13 matches
Mail list logo
