Wireshark · Wireshark-dev: Re: [Wireshark-dev] Wireshark-dev Digest, Vol 31, Issue 8

["Shouwei LI" <casmyu@xxxxxxxxx>]

Hello, everyboday:
Is there anybody have interesting to merge TUP protocol to wireshark?
I want to do this work. What's you opinion?
Best Regards!

On Fri, Dec 5, 2008 at 4:00 AM, <wireshark-dev-request@xxxxxxxxxxxxx> wrote:

Send Wireshark-dev mailing list submissions to
       wireshark-dev@xxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
       https://wireshark.org/mailman/listinfo/wireshark-dev
or, via email, send a message with subject or body 'help' to
       wireshark-dev-request@xxxxxxxxxxxxx

You can reach the person managing the list at
       wireshark-dev-owner@xxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wireshark-dev digest..."


Today's Topics:

  1. Re: [Wireshark-commits] rev 26904:        /trunk/plugins/unistim/
     /trunk/plugins/unistim/: packet-unistim.c (Joerg Mayer)
  2. Building Wireshark - Using nmake (philippe alarcon)
  3. Re: Building Wireshark - Using nmake (Graham Bloice)


----------------------------------------------------------------------

Message: 1
Date: Thu, 4 Dec 2008 10:31:57 +0100
From: Joerg Mayer <jmayer@xxxxxxxxx>
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 26904:
       /trunk/plugins/unistim/ /trunk/plugins/unistim/: packet-unistim.c
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <20081204093157.GF21516@xxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii

On Thu, Dec 04, 2008 at 12:20:25AM +0100, Jaap Keuter wrote:
> Care to comment on this one?
> Frankly I'm getting tired of going back and forth with this thing.
> Can't we sort it out once and for all?

The only comment I can give is, that in current svn head using port 5000
for Unistim still eats TAPA packets.
I've changed it back to the old comment and port 0

 ciao
    Joerg
--
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.


------------------------------

Message: 2
Date: Thu, 4 Dec 2008 17:26:58 +0100
From: philippe alarcon <philippe.alarcon@xxxxxxx>
Subject: [Wireshark-dev] Building Wireshark - Using nmake
To: <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <BAY123-W4974F4384EDFC431D597DA95020@xxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"


Hello,

I am trying to build the application under Windows XP.

In order to see if my environment is correct,
I have tried to build WSUTIL module.

I have used the basic command : nmake -f Makefile.nmake

My problem is that the make file doesn't find win32.mak.

I have not found this file.

Could somebody help me ?

Thanks in advance

Regards

_________________________________________________________________
In?dit ! Des Emotic?nes D?jant?es! Installez les dans votre Messenger !
http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.wireshark.org/lists/wireshark-dev/attachments/20081204/0b53e2f4/attachment.html

------------------------------

Message: 3
Date: Thu, 04 Dec 2008 16:42:37 +0000
From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Building Wireshark - Using nmake
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <4938087D.40500@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

philippe alarcon wrote:
> Hello,
>
> I am trying to build the application under Windows XP.
>
> In order to see if my environment is correct,
> I have tried to build WSUTIL module.
>
> I have used the basic command : nmake -f Makefile.nmake
>
> My problem is that the make file doesn't find win32.mak.
>
> I have not found this file.
>
> Could somebody help me ?
Have you followed the developers guide for setting up your windows dev
environment?
(http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html).

In particular, step 2.2.6.  I'm guessing that your path isn't good.

--
Regards,

Graham Bloice

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.wireshark.org/lists/wireshark-dev/attachments/20081204/28ab7305/attachment.htm

------------------------------

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev


End of Wireshark-dev Digest, Vol 31, Issue 8
********************************************