I built with VS 2008 and works in my wireshark version, but I also downloaded
the official 1.0.5 release and it didn’t work in it. What are the Microsoft CRT
dlls / where are they? Maybe ill try that. Though used the source from 1.1.2 or
1.1.3 so that could be my problem.
Greg
I'm trying to build wireshark v1.0.5. But i'm getting this error
C:\wiresharknmake -f makefile.nmake setup
Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
Copyright (C) Microsoft Corporation. All rights reserved.
config.nmake(439) : fatal error U1050: MSVC_VARIANT unknown
Stop.
2009/1/30 gogr...@wi.rr.com:
I'm trying to build wireshark v1.0.5. But i'm getting this error
C:\wiresharknmake -f makefile.nmake setup
Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
Copyright (C) Microsoft Corporation. All rights reserved.
config.nmake(439) : fatal
If I download the changed files would it be the same? Also, if I compile a
custom dissector plugin, will it work with the official 1.0.5 version?
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Quantin
Sent:
I am not an expert but, I just took a look at config.nmake and it says
# Microsoft Visual C++ 2008 Express Edition
# needs additional Platform SDK installation?
# Visual C++ 9.0, _MSC_VER 1500, msvcr90.dll
# With this variant, Wireshark will compile but fails to run!
#
# THIS VARIANT CURRENTLY
2009/1/30 gogr...@wi.rr.com:
If I download the changed files would it be the same?
Yes, you can try this. The corresponding revisions are 27186
(http://anonsvn.wireshark.org/viewvc?view=revrevision=27186) and
27200 (http://anonsvn.wireshark.org/viewvc?view=revrevision=27200)
Also, if I compile
Damn. Well I'm creating a custom dissector plugin for my company, which they
will want to use in versions of wireshark to come. What would be the best thing
to do so that my plugin will be compatible across many of the release versions?
Greg
-Original Message-
From:
So far, 1.0.X versions are built with MSVC6 and 1.1.X are built with
MSVC2008. You have 2 solutions:
- build 2 versions of your plugin
- try to build your custom plugin with MSVC2008 and ensure you embed
the manifest and distribute the CRT dlls with it. It should work
(there is already an ongoing
Ahh alright. Well if wireshark is going towards MSVC2008, then I might as well
use that. I don’t understand what these CRT dlls are and where I put them
though. Also, whats the mt.exe? Do i need to send out these CRT dll's if
everyone at the company has 2008? Also, do you think my best bet for
CRT files are the MS C runtimes libraries and are installed with MSVC.
You should ensure that your customer has those dlls installed so that
he can uses your plugin. That's why Microsoft provides free MSVC
runtimes installers. mt.exe is part of your MSVC installation and
allows to embed a manifest
Keep in mind, too, that the ABI for plugins is not stable. As such you
must compile your plugin for each version of Wireshark.
OK, you can probably get away with reusing a plugin between some
versions but there is no guarantee that the ABI won't change (and there
is no notice when it does
Darn. So does this mean that when the ABI changes, I will have to compile the
plugin with the new source?
Also, what is ABI?
Greg
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jeff Morriss
Sent: Friday, January
gogr...@wi.rr.com wrote:
Darn. So does this mean that when the ABI changes, I will have to compile the
plugin with the new source?
Yes.
Also, what is ABI?
http://en.wikipedia.org/wiki/Application_binary_interface
-Original Message-
From: wireshark-dev-boun...@wireshark.org
Hello
Couldn't load module C:\Program Files\Wireshark\plugins\1.0.5\ccs.dll:
The Specified module could not be found.
is the error window I have if I do not include the manifest inside the dll.
To include the manifest inside the dll :
mt.exe -manifest dll_name.dll.manifest
gogr...@wi.rr.com schrieb:
Darn. So does this mean that when the ABI changes, I will have to compile the
plugin with the new source?
Yes and no, see below.
Also, what is ABI?
Application Binary Interface
This is the interface provided by Wireshark to the plugins.
Some background
This ABI
The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/649
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: ubuntu-7.10-x86
Michael Tüxen schrieb:
That sound like an excellent idea...
Hmmm, I'm not that sure.
On Jan 29, 2009, at 10:16 AM, Guy Harris wrote:
On Jan 29, 2009, at 12:27 AM, Michael Tüxen wrote:
I like the idea, but I do not think that the SCTP related items
should
be moved there. It is correct
Jaap Keuter schrieb:
Hi,
Well that was easy:
grep 'everything with telephone icon' | xargs mv menu/Telephony
;)
No, even easier: There was already a menu group telephony, I only needed
to put this into a seperate menu ;-)
I'm oke with this idea, but would suggest to call it 'Telecom'
Hi!
Another patch I had lying around for months ...
The following will only have an effect on Windows based systems (I know
to little about Unix systems to do it right here) ...
If you have more than one or two capture interfaces (especially with the
usually long capture interface names on
The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/418
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build Reason:
Ulf Lamping wrote:
Jaap Keuter schrieb:
Hi,
Well that was easy:
grep 'everything with telephone icon' | xargs mv menu/Telephony
;)
No, even easier: There was already a menu group telephony, I only needed
to put this into a separate menu ;-)
Simple and elegant, I like it.
I'm oke
21 matches
Mail list logo
