On 13 November 2014 13:21, Maarten Bezemer maarten.beze...@gmail.com
wrote:
Hello,
This email is (a bit) long, as I am trying to explain the Wireshark
patches I
send, as requested by Graham Bloice.
Thanks for this, I was trying to understand what was going on from all the
fragments
.
If you get an incorrect scale value from the server to the client have you
tried Wireshark 1.12.2?
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http
On 13 November 2014 17:49, Alexis La Goutte alexis.lagou...@gmail.com
wrote:
On Thu, Nov 13, 2014 at 11:54 AM, Graham Bloice
graham.blo...@trihedral.com wrote:
Info for Windows devs, Microsoft have released this
(http://www.visualstudio.com/products/visual-studio-community-vs,
essentially
know whether that means you need MSVC
2013 or later to build ws_mempbrk_sse42.c. I also don't know whether, with
your change, ws_mempbrk_sse42.c still needs to include stdint.h on
Windows.
VS2010 also has stdint.h.
--
Graham Bloice
On 5 November 2014 11:31, Pascal Quantin pascal.quan...@gmail.com wrote:
2014-11-05 12:04 GMT+01:00 Graham Bloice graham.blo...@trihedral.com:
On 4 November 2014 20:34, Guy Harris g...@alum.mit.edu wrote:
On Nov 4, 2014, at 12:05 PM, Stephen Fisher
stephenfis...@centurylink.net wrote
On 5 November 2014 11:49, Pascal Quantin pascal.quan...@gmail.com wrote:
2014-11-05 12:42 GMT+01:00 Graham Bloice graham.blo...@trihedral.com:
On 5 November 2014 11:31, Pascal Quantin pascal.quan...@gmail.com
wrote:
2014-11-05 12:04 GMT+01:00 Graham Bloice graham.blo...@trihedral.com
On 18 October 2014 13:26, Alexis La Goutte alexis.lagou...@gmail.com
wrote:
On Fri, Oct 17, 2014 at 12:19 AM, Guy Harris g...@alum.mit.edu wrote:
On Oct 16, 2014, at 4:50 AM, Graham Bloice graham.blo...@trihedral.com
wrote:
Visual Studio (VS2013 at least) as 32 64 bit ARM compilers
fired them up though. I wonder if CMake can be persuaded to make solution
files that include ARM compilation options.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http
the
ability to hide dumpcap's console Window.
I wasn't sure if these were Bugs or Features and I needed to adapt my
driver accordingly. The overall functionality of Extcap is really nice
though.
Are you planning to share (if possible) and document this somewhere, e.g.
Wiki?
--
Graham
be the workaround?
cmake :-)
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options
changes...
In general Windows builds should be picking up the native Windows python as
the cygwin one is pretty slow.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http
to try a bit harder
to bring the QT build up to speed.
Note it's now The QT Company, Digia have taken a step back. See
http://blog.qt.digia.com/blog/2014/09/16/the-qt-company-introduces-a-unified-website-and-20e25-monthly-indie-mobile-package/
--
Graham Bloice
available anywhere?
--
Graham Bloice
___
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
with line-endings?
--
Graham Bloice
___
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
--
Graham Bloice
___
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
is that the chmod appears to make the directories
unreadable for the user I'm running the build with this re-running the
build fails. I'm inclined to think they can be removed.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
plugin
to PLUGIN_SRC_DIRS (along with a CMakeLists.txt for the actual plugin).
I see no reason why that couldn't be extended to include a
CustomCMakeLists.txt in the plugins directory.
--
Graham Bloice
___
Sent via
.
--
Graham Bloice
___
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
://code.wireshark.org/review/Documentation/user-notify.html
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https
When reviewing some submissions on Gerrit, I've noted a few with trailing
whitespace. The git pre-commit hook always warns me of this, so how are
folks managing to do this? Are they using clients that ignore the hook?
--
Graham Bloice
and the reviewer, as we all know
trailing white space is a heinous crime :-)
Did git-review install the hook for me, I can't think where else it came
from?
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev
On 25 August 2014 20:03, Joerg Mayer jma...@loplof.de wrote:
On Mon, Aug 25, 2014 at 06:06:15PM +0100, Graham Bloice wrote:
When reviewing some submissions on Gerrit, I've noted a few with trailing
whitespace. The git pre-commit hook always warns me of this, so how are
folks managing
On 22 August 2014 10:18, Thomas Wiens th.wi...@gmx.de wrote:
On 22 August 2014 00:03, Graham Bloice wrote:
Create a batch file containing something like:
REM Environment setup for Wireshark using VS2010
set CYGWIN=nodosfilewarning
set WIRESHARK_BASE_DIR=E:\Wireshark
set
merit in giving config.h a Wireshark specific name to
prevent conflicts form other packages, e.g. ws_config.h, as we haven't seen
any issues with that, I'll leave that as an exercise for others.
--
Graham Bloice
___
Sent via
can either consider the latest change as the primary
change and abandon the older one (which would effectively throw away Bill's
fine comments) or abandon the new change and resubmit your changes as a new
patch set to the older change.
--
Graham Bloice
cause difficulty with other out-of-tree
builds.
A solution might be to change the include in extcap.h to be #include
config.h so the current directory isn't searched, but that seems a bit
hackish to me.
--
Graham Bloice
On 21 August 2014 10:04, Guy Harris g...@alum.mit.edu wrote:
On Aug 21, 2014, at 1:57 AM, Graham Bloice graham.blo...@trihedral.com
wrote:
This obviously worked before the merge of ExtCap, so that has disturbed
things. The CMake build should be using the generated one in the CMake
build
\nghttp2\nghttp2_helper.h(28): #include config.h
ui\qt\main_window_slots.cpp(22): #include config.h
ui\qt\search_frame.h(25): #include config.h
Found 5 occurrence(s) in 5 file(s)
--
Graham Bloice
___
Sent via:Wireshark-dev
at the Mac buildbot (GLib 2.34 is the issue) right now, and
maybe have a solution for that in the afternoon.
Just changing that include doesn't fix the Windows CMake build
unfortunately. See attached file.
--
Graham Bloice
E:\Wireshark\build2013\Wireshark.sln (default target) (1
?
Have a look at the Wiki page on submitting patches:
http://wiki.wireshark.org/Development/SubmittingPatches which advises using
the Gerrit helper git-review
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
,
distclean, maintainer-clean build as well.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org
onwards (it's added
automagically by the VC batch files), and we're moving to VS2013 for master
so you should try to move to that as well if you aren't already there.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing
The -OlderThan dynamic parameter was only added in Powershell 3.0. We'll
have to figure out a solution that works in PS 2.0
Probably replacing `Test-Path $dst_file -OlderThan` with `(Get-Item
$dst_file).LastWriteTime -lt `
--
Graham Bloice
non-zero exit status 1
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options
wrong with the new screen?
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options
./README.windows
--
Graham Bloice
___
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
On 15 August 2014 15:13, Anders Broman anders.bro...@ericsson.com wrote:
*From:* wireshark-dev-boun...@wireshark.org [mailto:
wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice
*Sent:* den 15 augusti 2014 16:05
*To:* Developer support list for Wireshark
*Subject:* Re
On 15 August 2014 15:29, Anders Broman anders.bro...@ericsson.com wrote:
*From:* wireshark-dev-boun...@wireshark.org [mailto:
wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice
*Sent:* den 15 augusti 2014 16:20
*To:* Developer support list for Wireshark
*Subject:* Re
. The item has to be at + 2 and then you can hit the Submit button.
There is no mandatory Petri-Dish flag yet.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http
at your top level source directory:
code
$env:Path += ;PATH\TO\QT\BIN
windeployqt --release --no-compiler-runtime --list relative
wireshark-qt-release\qtshark.exe
/code
--
Graham Bloice
___
Sent via:Wireshark-dev mailing
On 11 August 2014 13:45, Anders Broman anders.bro...@ericsson.com wrote:
*From:* wireshark-dev-boun...@wireshark.org [mailto:
wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice
*Sent:* den 11 augusti 2014 14:04
*To:* Developer support list for Wireshark
*Subject:* Re
On 11 August 2014 15:21, Anders Broman anders.bro...@ericsson.com wrote:
*From:* wireshark-dev-boun...@wireshark.org [mailto:
wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice
*Sent:* den 11 augusti 2014 15:18
*To:* Developer support list for Wireshark
*Subject:* Re
On 11 August 2014 17:19, Gerald Combs ger...@wireshark.org wrote:
On 8/11/14 7:53 AM, Graham Bloice wrote:
On 11 August 2014 15:21, Anders Broman anders.bro...@ericsson.com
mailto:anders.bro...@ericsson.com wrote:
__ __
__ __
*From:*wireshark-dev-boun...@wireshark.org
think we should maybe
get the installer to check if the host OS is XP, and then offer the warning
before doing anything else.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives
look to move right now, the clock is
definitely into overtime.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https
On 7 August 2014 16:04, Christopher Maynard christopher.mayn...@gtech.com
wrote:
Graham Bloice graham.bloice@... writes:
qtshark won't run from the wireshark-qt-release directory as not all the
required DLL's have been copied over.
If you add %QT5_BASE_DIR%\bin to your %PATH
On 6 August 2014 00:12, Joerg Mayer jma...@loplof.de wrote:
On Tue, Aug 05, 2014 at 12:33:30PM +, Wireshark code review wrote:
8b2a8a9 by Graham Bloice (graham.blo...@trihedral.com):
Suppress 10 of the CMP0020 CMake warnings on Windows, only 8 left
now.
I had so hoped you would
.
Is your source tree modified? If so please try to compile a plain
unmodified version first.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists
in preferences but didn't see anything).
Thoughts?
+1 but i not sure if it is possible...
I find it useful, although when I find a self+2 commit that breaks the
build without the PD flag it makes me want to rant.
--
Graham Bloice
under this circumstances ?
P.S.: I'm not subscribed, please Cc: me.
This did come up before the move to Gerrit, see the mails starting here:
http://www.wireshark.org/lists/wireshark-dev/201401/msg4.html
I'm not sure what the outcome was for Joerg though, but he does use Gerrit.
--
Graham
The x86 CMake build now completes :-)
The x64 build is failing due to the lack of an acceptable Python and some
dumpcap link errors.
On 1 August 2014 00:28, Gerald Combs ger...@wireshark.org wrote:
On 7/31/14 2:19 PM, Graham Bloice wrote:
On 31 July 2014 22:14, Graham Bloice graham.blo
on it though.
--
Graham Bloice
___
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
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote:
On 7/31/14 6:08 AM, Graham Bloice wrote:
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu
mailto:bal...@balintreczey.hu wrote:
+1 for dropping autotools in favor of CMake. CMake already covers all
my use
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote:
On 7/31/14 6:08 AM, Graham Bloice wrote:
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu
mailto:bal...@balintreczey.hu wrote:
+1 for dropping autotools in favor of CMake. CMake already covers all
my use
On 31 July 2014 22:14, Graham Bloice graham.blo...@trihedral.com wrote:
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote:
On 7/31/14 6:08 AM, Graham Bloice wrote:
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu
mailto:bal...@balintreczey.hu wrote:
+1
/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org
?subject=unsubscribe
--
Graham Bloice
Software Developer
Trihedral UK Limited
On 28 July 2014 13:35, mman...@netscape.net wrote:
+1
I was trying to hold out until the CMake stuff for Windows is complete.
Since it sounds close, I thought I could just deal with merging the removal
of O2 option for awhile.
Feedback on the latest CMake changes I added to Gerrit wold
the minimum supported for master.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman
On 24 July 2014 18:51, Pascal Quantin pascal.quan...@gmail.com wrote:
Le 24/07/2014 19:39, Joerg Mayer a écrit :
On Thu, Jul 24, 2014 at 06:20:48PM +0100, Graham Bloice wrote:
On 24 July 2014 18:08, Joerg Mayer jma...@loplof.de wrote:
IIRC there was some discussion which versions of VS
really.
--
Graham Bloice
___
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
On 24 July 2014 19:03, Pascal Quantin pascal.quan...@gmail.com wrote:
Le 24 juil. 2014 20:00, Graham Bloice graham.blo...@trihedral.com a
écrit :
On 24 July 2014 18:51, Pascal Quantin pascal.quan...@gmail.com wrote:
Le 24/07/2014 19:39, Joerg Mayer a écrit :
On Thu, Jul 24, 2014
On 24 July 2014 19:06, Graham Bloice graham.blo...@trihedral.com wrote:
On 24 July 2014 19:03, Pascal Quantin pascal.quan...@gmail.com wrote:
Le 24 juil. 2014 20:00, Graham Bloice graham.blo...@trihedral.com a
écrit :
On 24 July 2014 18:51, Pascal Quantin pascal.quan...@gmail.com wrote
On 24 July 2014 20:02, Graham Bloice graham.blo...@trihedral.com wrote:
On 24 July 2014 19:06, Graham Bloice graham.blo...@trihedral.com wrote:
On 24 July 2014 19:03, Pascal Quantin pascal.quan...@gmail.com wrote:
Le 24 juil. 2014 20:00, Graham Bloice graham.blo...@trihedral.com a
écrit
:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org
?subject=unsubscribe
--
Graham Bloice
Software Developer
Trihedral UK Limited
On 16 July 2014 06:36, Pascal Quantin pascal.quan...@gmail.com wrote:
Le 16/07/2014 00:18, Guy Harris a écrit :
On Jul 15, 2014, at 2:03 PM, Graham Bloice graham.blo...@trihedral.com
wrote:
I'm going to add some info to the developers guide for building with
VS2013, I'll probably add
On 15 July 2014 23:18, Guy Harris g...@alum.mit.edu wrote:
On Jul 15, 2014, at 2:03 PM, Graham Bloice graham.blo...@trihedral.com
wrote:
I'm going to add some info to the developers guide for building with
VS2013, I'll probably add VS2012 although MS seems to regard that as dead
as the EE
* KERBEROS
* PythonInterp
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options
of a changeset that caused a build to
give me a link I can click on to get the diffs of the commit, along with a
more suitable title and tooltips than Gerrit: patchset(s) merged?
--
Graham Bloice
___
Sent via:Wireshark-dev
I'm going to add some info to the developers guide for building with
VS2013, I'll probably add VS2012 although MS seems to regard that as dead
as the EE version isn't available any more.
Any objections if I remove all the stuff about ancient compilers pre VS2010?
--
Graham Bloice
On 13 July 2014 19:59, Alexis La Goutte alexis.lagou...@gmail.com wrote:
On Fri, Jul 11, 2014 at 7:55 PM, Gerald Combs ger...@wireshark.org
wrote:
On 7/10/14 9:28 AM, Graham Bloice wrote:
Folks,
Can we consider moving to VS2013 for the windows builds, maybe moving
the Win 8.1 buildbot
.
--
Graham Bloice
___
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
On 10 July 2014 07:30, Graham Bloice graham.blo...@trihedral.com wrote:
On 10 July 2014 02:06, Guy Harris g...@alum.mit.edu wrote:
On UN*X, the file names for libraries begin with lib - the linkers all
look for libfoo.* if you link with -lfoo.
On Windows, that's not the case.
Is there any
Folks,
Can we consider moving to VS2013 for the windows builds, maybe moving the
Win 8.1 buildbot to use it?
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http
On 3 July 2014 18:20, Alexis La Goutte alexis.lagou...@gmail.com wrote:
Hi,
I'm OK to backport this serie of patch to 1.12
Other core ?
I want also try to also add to backport 1.12 change about HTTP2
(include nghttp2 lib)
I wouldn't like to backport nghttp2 until we get the build for
On 3 July 2014 18:38, Pascal Quantin pascal.quan...@gmail.com wrote:
2014-07-03 19:26 GMT+02:00 Graham Bloice graham.blo...@trihedral.com:
On 3 July 2014 18:20, Alexis La Goutte alexis.lagou...@gmail.com wrote:
Hi,
I'm OK to backport this serie of patch to 1.12
Other core ?
I want also
.
--
Graham Bloice
___
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
, their detection of what is a debug and
release build is failing for some reason with qtshark.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists
On 24 June 2014 16:26, Anders Broman a.broma...@gmail.com wrote:
Den 24 jun 2014 16:49 skrev Graham Bloice graham.blo...@trihedral.com:
On 24 June 2014 15:41, Anders Broman anders.bro...@ericsson.com wrote:
Hi,
I think with Qt5.2 there is more dlls and new subdirectories
)
It works pretty well for me with Qt5.2 / Qt5.3
Eventually we'll get cmake working properly, I have no idea what cpack does
though.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives
\RelWithDebInfo.
CMakeLists.txt should be adjusted to build and link these libraries.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists
, in the future, to use newer Windows API
functions that aren't present on Win2K, and if\when we do so, then that
build won't run on Win2K.
Comments?
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev
On 18 June 2014 13:12, wsgd w...@free.fr wrote:
Le 18/06/2014 00:41, Pascal Quantin a écrit :
2014-06-18 0:11 GMT+02:00 Pascal Quantin pascal.quan...@gmail.com:
2014-06-16 22:44 GMT+02:00 wsgd w...@free.fr:
Hello,
My protocol (only to test this problem) specifications :
tcp port
On 12 June 2014 09:15, Giorgio Buffa buffagior...@gmail.com wrote:
Hi Graham,
thanks a lot for the detailed explaination. I got stucked on point #4: *From
the Start Menu (or Screen for Win 8+) open a Visual studio Command prompt
for the type of build you are making (x86 or x64).*
How do I
On 11 June 2014 16:21, Gerald Combs ger...@wireshark.org wrote:
The Visual Studio team recently announced that major changes are coming
for the C Runtime in VS 14, namely that they are switching to a set of
single stable releases:
installer built may not install all the required DLL's for QT, that's
still a work in progress at the moment.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http
On 5 June 2014 10:00, Graham Bloice graham.blo...@trihedral.com wrote:
On 5 June 2014 07:18, Joerg Mayer jma...@loplof.de wrote:
Hello (at least Graham),
I'd like to get as far with the cmake on Windows stuff as possible during
Sharkfest I thought we might as well start early ;-)
What do
On 5 June 2014 07:18, Joerg Mayer jma...@loplof.de wrote:
Hello (at least Graham),
I'd like to get as far with the cmake on Windows stuff as possible during
Sharkfest I thought we might as well start early ;-)
What do we need to address in the cmake build system to be able to propose
-qt-release\printsupport\windowsprintersupportd.dll
After this qtshark runs.
Note windeployqt will also copy all the files as well as list them, I think
we should use it in the build.
--
Graham Bloice
___
Sent via
On 3 June 2014 22:59, Graham Bloice graham.blo...@trihedral.com wrote:
Experimenting using VS2013 (Pro) to build Wireshark, I ran into some QT
issues and for posterity thought I'd list them here:
1. You need a VS2013 compatible version of QT, I used
qt-opensource-windows-x86-msvc2013
On 21 May 2014 15:37, Anders Broman anders.bro...@ericsson.com wrote:
*From:* wireshark-dev-boun...@wireshark.org [mailto:
wireshark-dev-boun...@wireshark.org] *On Behalf Of *Raul Felice
*Sent:* den 20 maj 2014 17:48
*To:* wireshark-dev@wireshark.org
*Subject:* [Wireshark-dev] Dynamic
On 27 April 2014 23:16, Richard Sharpe realrichardsha...@gmail.com wrote:
On Sun, Apr 27, 2014 at 3:09 PM, Pascal Quantin
pascal.quan...@gmail.com wrote:
Le 28 avr. 2014 00:06, Richard Sharpe realrichardsha...@gmail.com a
écrit :
On Sun, Apr 27, 2014 at 1:41 PM, Richard Sharpe
On 23 April 2014 14:14, Evan Huus eapa...@gmail.com wrote:
On Wed, Apr 23, 2014 at 9:11 AM, Anders Broman
anders.bro...@ericsson.com wrote:
In my benchmarks it is measurably slower than GHashTable, but not
excessively
so. Given the additional security it provides this seems like
will supply VS licences for open source
projects, do you know anything about that Gerald?
[1] :
http://ask.wireshark.org/questions/31771/new-build-1106-on-vs2012-missing-msvcr100dll
--
Graham Bloice
___
Sent via:Wireshark-dev
On 16 April 2014 16:03, Anders Broman anders.bro...@ericsson.com wrote:
I couldn’t install Visual studio 2013 on my work computer as it complained
Explorer was too old, unfortunately I can’t upgrade Explorer so I’d vote
for 2012 J
Anders, you have to give up on XP at some point :-)
Or do
Hi Pavel,
Can you use the revised workflow and submit the change to Gerrit. Any
discussion on the proposed change will take place in the Gerrit Review
process.
Workflow info can be found here:
http://wiki.wireshark.org/Development/Workflow
On 28 March 2014 15:06, Pavel Karneliuk
On 20 March 2014 11:21, Rahul Rohit rahul.ro...@aricent.com wrote:
Hi,
Is there any way by which Wireshark can capture packets for loopback
traffic (when the source and destination ip are same)on windows or linux
machine.
See the loopback capture page on the Wiki:
A recent question on Ask Wireshark (
http://ask.wireshark.org/questions/30890/makensis-makensis-path)
Gerald made a change (
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commitdiff;h=dc87fa2d68a5dbc7693b5cc93e044a62af5ce39c)
to set the NSIS path, but I'm a bit puzzled by it.
On all
On 12 March 2014 03:00, mman...@netscape.net wrote:
My biggest frustration is noted by the statement:
However, as most use on other platforms tends to be command-line git,
most books and guides tend to concentrate on that so windows users may
actually find it easier to start with the command
-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-requ...@wireshark.org
?subject=unsubscribe
--
Graham Bloice
Software Developer
Trihedral UK
: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-requ...@wireshark.org
?subject=unsubscribe
--
Graham Bloice
Software
501 - 600 of 935 matches
Mail list logo
