The .nmake files are for windows use, and I've had problems using the
Custom.nmake file for windows also, so I use the ordinary makefile in epan. (I
forgot its name just now).
BR
Tobias W
-Original Message-
From: wireshark-dev-boun...@wireshark.org
That is because there isn't any solution file. The build is done via command
line, but you can build from visual studio using the nmake tools also using a
batch-file that calls the nmake command. That is how I solved it in VS 2003
since I couldn't get it to work by using the command directly. I
dissector_add(tcp.port, portnumber, protocol_handle);
It should be an example dissector in the README.developer that has this
information.
/Tobias
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Corraine
(mcorrain)
Sent: den 11 juni 2008 16:45
Hi
I'm not fully immersed of the details of the build process, but I think (well
know, but I'm a bit modest... ;) ) it has to do with dependencies. The
C:\wireshark-1.0.0\ folder and all subfolders except for those created during a
build (to see the effect do a 'nmake -f Makefile.nmake
Hello Chris,
I'd say that it's possible. I'm doing a thesis work in the same direction,
though not using XML but a language I constructed for this (Yet Another
Language, I know... ;) and it's going quite well.
I haven't announced this before, but as I'm near completion of the work (it's
/Makefile.nmake. Now I've ran in to some other compilation problems,
but I they seem to be local to my other libraries and is probably provoked by
an update I did not long ago.
Regards,
Tobias Wärre
PS I downloaded the tarball that was linked from the e-mail that Gerald Combs
sent us earlier today. DS
