A follow-up on issues when building wireshark on win32.
I found out that if Cygwin make package is installed, Wireshark cannot
be built anymore under win32 (cannot find cl and other dependencies).
It might be a conflict between Cygwin's make and nmake.
Does someone else have the issue? For
for Wireshark
Subject: Re: [Wireshark-dev] win32: nmake setup: can't find cl
Works fine for me, but then I don't have Cygwin on my normal
path. Do you?
No I don't have Cygwin in my path. Do you have Cygwin's make package
installed? In this case, it works for me too if I don't have the
makefile.nmake
verify_tools showed that Cygwin python was available on your system then.
From a bash shell what does env python produce?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman
and I'm not entirely sure what that
could be.
As a workaround, from within your bash shell navigate to epan/dissectors
and run the command:
python ncp.py -o packet-ncp.c
This should allow your build to proceed.
--
Regards,
Graham Bloice
used to use a native python (I believed that it was faster), but
switched back to the default cygwin one time time ago with no problems
at all.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
Douglas Pratley wrote:
The wiki tips page has a couple of useful sections on debugging and
setting up browse info for MSVC.
http://wiki.wireshark.org/Development/Tips
You might also consider using WinDbg. It now has a GUI and once you get
the symbol and source paths sorted out
,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
I'm updating an older dissector (dnp3) and it uses a g_malloc() to build
a tmp buffer of data extracted in chunks from the tvb. A new tvb is
then created from this tmp buffer. After the new tvb (created by a call
to tvb_new_real_data()) is created the tmp buffer isn't used.
Which emem version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Graham Bloice wrote:
I've been attempting to add tcp fragment reassembly using
tcp_dissect_pdus() to an existing dissector that already used the epan
reassembly code for an internal part of the protocol.
However it seems that when I add
source?
Not that I know of. Why do you feel that you need to use a project?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
.
If the problem persists, contact the program software vendor.
The version of U3 Launchpad in use is 1.4.0.2
--
Regards,
Graham Bloice
Software Developer
Trihedral UK Limited
Tel: +44 (0)7002 874433
___
Wireshark-dev mailing list
Wireshark-dev
Graham Bloice wrote:
I built a U3 version from SVN 20915, but the resulting .u3p fails to
install on my SanDisk MicroCruzer.
When I run the U3 add programs applet, it reports:
U3 Launchpad failed to install U3 program, due to a possible error in
the program package. Try downloading
Graeme Lunt wrote:
Hi,
Graham Bloice wrote:
I built a U3 version from SVN 20915, but the resulting .u3p fails to
install on my SanDisk MicroCruzer.
Does the package downloaded from:
http://prdownloads.sourceforge.net/wireshark/wireshark-0.99.5.u3p
install OK?
Yes it does, without
?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
to prefixing standard symbols with the letter g because
somebody decided to reinvent the wheel.
See comment above. The glib types help with a greater portability than
SUSv3.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
' to 'int ',
possible loss of data
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
.
--
Regards,
Graham Bloice
mpeg.c.diff.gz
Description: application/gzip
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
: unresolved
external symbol _mpa_versions
libwireshark.dll : fatal error LNK1120: 6 unresolved externals
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Graham Bloice wrote:
ronnie sahlberg wrote:
modified and checked in
2006-08-25 Shaun Jackman [EMAIL PROTECTED]
* asn1/Makefile.am (EXTRA_DIST): Add mpeg.
* asn1/mpeg/Makefile: New file.
* asn1/mpeg/mpeg-audio.asn: Ditto.
* asn1/mpeg/mpeg-audio.cnf: Ditto.
* asn1/mpeg/mpeg-pes.asn
defined, which is
indicated by the symbol _WINSOCK2API_. I think that using this symbol
would be preferable.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Ulf Lamping wrote:
Graham Bloice wrote:
When compiling with MSVC 6.0 and the platform SDK, there are failures
due to the redefinition of sockaddr_storage in capture_wpcap_packet.c
and gtk/capture_if_details_dlg.c.
The definition is conditional on the version of MSVC used, whereas the
actual
Gisle Vanem wrote:
The #pragma warning() statements are MSVC specific. So
embed them inside #ifdef _MSC_VER.
I always thought unrecognised #pragma directives were ignored. I take
it that MinGw barfs on them in some way?
--
Regards,
Graham Bloice
Gisle Vanem wrote:
Graham Bloice [EMAIL PROTECTED] wrote:
Gisle Vanem wrote:
The #pragma warning() statements are MSVC specific. So
embed them inside #ifdef _MSC_VER.
I always thought unrecognised #pragma directives were ignored. I take
it that MinGw barfs on them in some way?
MingW
have VS 2005, so moving isn't an issue
for me, but should we consider dropping support for earlier VC versions.
This might clean up a few things.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
Ulf Lamping wrote:
Graham Bloice wrote:
On MSVC 6.0 + PDSK, I had to remove the Wx from CFLAGS to allow
compilation to proceed due to a warning emitted when compiling
packet-parlay.c.
The warning was that the number of lines exceed an internal limit
(65536) and no more line number info
local hard disk. Continue as per the developers guide.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
. Click OK.
After a suitable period of time you should have the source tree on your
local hard disk. Continue as per the developers guide.
--
Regards,
Graham Bloice
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev
installation.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
,
but not for a long time.
Others have built it using VS2003, VS2005 and VS2005EE. I have no idea
what OS they used.
The tool depends.exe can be of use to find out what DLL's an exe expects
to use.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev
Ulf Lamping wrote:
Graham Bloice wrote:
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows
Server 2003 R2\Bin and not the directory mentioned in the developper's
guide (Visual studio dir). Is it normal ?
The paths shown in the dev guide
better base to prevent new warnings from
leak into the sources.
Our mission continues ...
Thanks for rousing us into action. It had grated with me for a long
time, but I didn't have your resolve, nor Sebastian's commitment.
--
Regards,
Graham Bloice
easier.
I don't think it makes much difference. The loader will check for the
manifest in both places and the assemblies identified in the manifest
must be available.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
the #ifdef _WIN32
block down to below the other includes fixes it as including winsock2.h
first will stop the winsock.h attempting to redefine things.
Another similar occurrence is in gui_utils.c. I've checked in fixes in
r21335.
--
Regards,
Graham Bloice
like to point out that a list of compiler errors is not very
helpful without a context, i.e. the compiler line that preceded the errors.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org
Clifford Thrasher wrote:
Graham Bloice wrote:
Graeme Lunt wrote:
Hi,
Graham Bloice wrote:
I built a U3 version from SVN 20915, but the resulting .u3p fails to
install on my SanDisk MicroCruzer.
Does the package downloaded from:
http
about a missing procedure entry point _encode_pointer in
msvcr80.dll. This appears to be called from zlib1.dll.
Note that I'm also using the rebuilt zlib1.dll required for use with
VS2005. Wireshark itself runs fine.
--
Regards,
Graham Bloice
that the test ran successfully.
So, the test needs to build the exe, copy reassemble_test.exe and
reassemble_test.manifest to the wireshark-gtk2 dir, then execute the exe
from there. I think that will be easier than trying to fiddle the path.
--
Regards,
Graham Bloice
, but in the long run this will help us keep agile and
provide the features that are most important today.
Enjoy!Network Monitor Team
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman
and the Wireshark 0.99.4 sources.
One of the disassemblers I tried reported: Resource Table is Missing.
Any ideas?
It looks like the resources weren't compiled into your dll's for some
reason. I think you might be out of luck :-(
--
Regards,
Graham Bloice
Folks,
The win32 buildslave is now compiling again, but fails the tests.
My build seems to work OK. Is it something in the test environment?
--
Regards,
Graham Bloice
Software Developer
Trihedral UK Limited
Tel: +44 (0)1224 258910
___
Wireshark-dev
?
Does VS2005 EE not install a Visual Studio 2005 Command Prompt entry
in the Visual Studio Tools menu of VS?
VS 2005 Professional certainly does. The advantage of this is the paths
will be correct. All you need to do is copy it and change the Start
in directory.
--
Regards,
Graham Bloice
this in a
similar manner to zlb?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
is there, but presume because of some upset due to the first
issue things aren't right.
Can the tcp reassembly experts have a look at this?
--
Regards,
Graham Bloice
cap12.pcap
Description: Binary data
___
Wireshark-dev mailing list
Wireshark-dev
Graham Bloice wrote:
Folks,
In the DNP3 dissector I am using tcp_dissect_pdus() to handle data
across multiple tcp segments. It mostly works but in the attached
capture things go a bit awry.
The DNP3 data consist of 2 pdus, the first is 292 bytes, the second is
178 bytes. The first pdu
.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
.dsw) in VS2005, convert it to
the VS2005 project format and rebuild it. Link wireshark again and you should
be good to go.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo
8\Common7\Tools\) to set
the build environment.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
in them.
Any suggestions would be great.
Try grabbing Dependency Walker from http://www.dependencywalker.com/. Run it
on your .exe to see what it's complaining about. Make sure you run it on the
target systems that are complaining.
--
Regards,
Graham Bloice
Graham Bloice wrote:
Alex Lindberg wrote:
I am using MS C++ 2005 Express Edition with the platform SDK (Version
3790.2075).
All compiles and packages fine with no errors.
After packaging and installing on a W2k machine, it responds as above.
I am using the the updated C++ 2005 vcredist
the trunk version from svn. You don't tell us what build
environment you're using either.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
. To help
with the debugging, make sure you have a symbol cache setup pointing to the MS
Symbol Server (Tools | Options | Debugging | Symbols and then F1 for the help,
read this and then look for How to: Use a Symbol Server).
--
Regards,
Graham Bloice
to this.
Is anyone looking at this at all?
--
Regards,
Graham Bloice
badclass0.cap
Description: Binary data
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
treatment.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
http://anonsvn.wireshark.org/viewvc/viewvc.py/releases/, although it appears
that 0.99.6 has it's own little special place at the moment. Gerald?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
the trunk and then update to the revision you want.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
, but the description of option
249 in packet-bootp.c already caters for that.
I modified the dissector to do the same decoding for option 249 and it works
fine for me.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
has two different icons (one for docs) each with
5 different sizes in 256 colours only; 16x16, 24x24, 42,32, 48,48, 64x64.
GTK may impose other requirements that I'm not aware of.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev
debugger.
4. When prompted, point VS at your source file location.
--
Regards,
Graham Bloice
Software Developer
Trihedral UK Limited
Tel: +44 (0)1224 258910
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman
should
remove this warning)
Does anybody have an idea how i can apply my preferences to disable this
warning?
From the Edit menu, select Preferences, then click the Apply button.
--
Regards,
Graham Bloice
in your build environment?
If anyone else is building with VS 2005 EE *and* the resulting
executables work on W2K, can they please post what SDK they are using.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
in
the Win32 build guide.
As the main win32 build is still produced using 6.0 I would think so. I
stopped using it about 4 months ago so I can't comment myself. You
might still run into the same issue though using the W2K3 SDK.
--
Regards,
Graham Bloice
the issue has stayed the course until we resolved it.
You may want to buck the trend!
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
The buildbot is reporting a permission problem.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
the output of path from your build
environment. What is the result of nmake -f makefile.nmake verify_tools ?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
.
Anyone has a clue or should I really try a newer version??
Best to try a newer version. Ensure your build environment is set up
correctly as per the developers guide. See
http://www.wireshark.org/docs/wsdg_html/#ChSetupWin32 for more info.
--
Regards,
Graham Bloice
An almost correct article on Wireshark can be found at:
http://tinyurl.com/ysdhy2
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
anyone else seen anything like this?
What compiler version?
If you're on Windows, and using a version of MSVC later than 6.0, have
you recompiled the adns library? setup removes the old one.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Peter Johansson wrote:
2007/10/1, Graham Bloice [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]:
Peter Johansson wrote:
2007/10/1, Graham Bloice [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]:
Peter Johansson
-05\adns_win32\lib.
I have very similar issues if I *don't* rebuild adns_dll.dll, afterwards
all is fine.
Try checking the dll with depends. A properly rebuilt dll depends on
msvcr80.dll, the original depends on msvcrt.dll.
--
Regards,
Graham Bloice
using MS Visual C++ 6.0 on Windows XP with cygwin.
I would suspect a path issue possibly related to the Platform SDK
headers. The headers in the error message are the standard VC 6 ones.
What is the value of path in your build environment?
--
Regards,
Graham Bloice
Michael Lum wrote:
My path is as follows:
Ah. What I meant ask is what is the value of the INCLUDE var in your
build environment.
Although from your path, it does look like you don't have the SDK
installed\setup.
--
Regards,
Graham Bloice
Software Developer
Trihedral UK Limited
Tel: +44
be interested to know if the buildbot
(which still uses VC6) has the SDK installed. Maybe Gerald can comment.
There have been a number of changes in the makefiles since 0.99.4 so
that might account for your difficulties.
--
Regards,
Graham Bloice
___
Wireshark
yourself is Cygwin the MS toolchain, as detailed in the developers guide.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
makefile.nmake filesystem.obj
2. Copy the compiler invocation emitted by nmake and paste it back into
your command prompt, but tack a -P on the end
3. This should produce a filesystem.i for your perusal. Good luck.
--
Regards,
Graham Bloice
___
Wireshark-dev
compile
without the SDK, we found that code just didn't run very well when
exposed to different platforms.
Just as a thought, you do have the latest SP for VC6 installed don't you?
Apart from that have you thought about moving to VC2005EE ?
--
Regards,
Graham Bloice
Might be interesting for some:
binpac: A yacc for Writing Application Protocol Parsers
http://lambda-the-ultimate.org/node/2496
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman
beat me to it with r23222, but I went a little further and resorted
the file in case-insensitive ascending order. Note that despite your
text above and the commit comment, the correct symbol was added
(eth_stdio_fopen). The build worked for me (VS2005 Pro).
--
Regards,
Graham Bloice
in the
developers guide *to the letter*.
GetTextMetricsW is a unicode function in gdi32.lib. Either your build
environment is broken so badly that gdi32.lib isn't on the link path, or
you're trying to do something odd on a non-unicode win32, e.g. 9x.
--
Regards,
Graham Bloice
,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Currently the win32 Makefile.nmake calls for WpdPack 3.1. As the
current version is 4.0.2 shouldn't this be updated?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo
\n
make.exe' : return code '0x2'
Stop.
C:\wireshark
You'll need to provide more info, specifically the messages printed just
before the above. All I can tell is that the MS compiler choked on
something.
--
Regards,
Graham Bloice
___
Wireshark-dev
mkdir d
which is what you would have to type if extensions were disabled.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
code I have add.
Could you please help me to solve this problem?Thanks!
If you could explain *exactly* what you're doing, i.e. what commands
you're typing, then someone may be able to explain how to make things
better.
--
Regards,
Graham Bloice
.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
seem that your include path includes some cygwin directories.
Can you post the output of set INCLUDE ,and for good measure set LIB?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman
using MSVC 2005 EE.
I have attached the point at which the compilation failed
Are you using a command shell other than the standard cmd.exe?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org
haven't responded to Steven's request. I'll try to
do so tomorrow.
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Stig Bjørlykke wrote:
On 21. feb.. 2008, at 20.49, Graham Bloice wrote:
This is very symptomatic of using an original adns dll compiled with
MS
VC 6 against a later C runtime. Are you sure you've compiled a new
dll? Did you do a setup and get the old one back?
Ah
leading up to the error.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
files\microsoft visual
studio\VC98\Bin\nmake.exe ':return code '0X2'
Stop
Unfortunately I assumed that the error would be in the preceding lines,
but it looks like it was earlier. Can you supply the whole of the nmake
output as a text attachment.
--
Regards,
Graham
/bugzilla/show_bug.cgi?id=2075 for an
attempt to fix the adns issue with versions other than MSVC 6. If we
are going to contact jgaa, updating his makefiles to allow CFLAGs to be
passed in would be nice as well.
--
Regards,
Graham Bloice
___
Wireshark
for something to do
with wireless comms.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Freexxx() functions that seem to handle freeing
allocations that the lib makes.
From the web site, they also have a link to other similar libs, Poslib
(http://posadis.sourceforge.net/) and UDNS
(http://www.corpit.ru/mjt/udns.html) look interesting.
--
Regards,
Graham Bloice
but I have to ask why you want to do this? You've
already drunk the MS Koolaid by running XP, how are the free VS Express
compilers not meeting your needs?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
there is the standard *nix stuff for
building on *nix platforms I don't think anyone has attempted to use
that on windows for a long time. I believe that someone once managed to
get it to build under Cygwin.
I wish you luck in your endeavours.
--
Regards,
Graham Bloice
are still getting errors have you set up the Visual Studio env vars
by the steps in 2.2.6 of the guide?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
as
that file is being automatically generated in build process and everytime
You make distclean the same problem will be reproduced during the
build process
Try searching the archives. This has come up before.
--
Regards,
Graham Bloice
___
Wireshark-dev
API for
plugins to use?
Did you rebuild libwireshark.dll with the new .def file so that it the
linker marked the functions as exported?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
https://wireshark.org
1 - 100 of 935 matches
Mail list logo
