[Rohan Solanki <solanki.rohan@xxxxxxxxx>]

Thanks a lot.... I'll try this.....
I am from India... Just want to know where are u from? because i want to know the timings that we can chat? Here the time is around 10 pm.....

Thanks in advance......

On Thu, Apr 23, 2009 at 9:30 PM, Sean <seanbzd@xxxxxxxxx> wrote:

Try this:

1st command will work only if visual studio bin folder is in the PATH. If its not there, just navigate to where the batch file is located and run it from there

C:\Program Files\Wireshark\wireshark-1.0.5>vcvars32

C:\Program Files\Wireshark\wireshark-1.0.5>nmake -f Makefile.nmake verify_tools

C:\Program Files\Wireshark\wireshark-1.0.5>nmake -f Makefile.nmake all

On Thu, Apr 23, 2009 at 11:49 AM, Rohan Solanki <solanki.rohan@xxxxxxxxx> wrote:

Can you please tell me the steps you follow to compile.. What i have done is:- 1) Downloaded the source 2) Downloaded all the softwares needed..(python, perl etc that comes with cygwin and platform sdk)...

Thanks

On Thu, Apr 23, 2009 at 9:09 PM, Sean <seanbzd@xxxxxxxxx> wrote:

If you post the errors you are getting, it would be useful. I usually run the batch file from the command line before building anything using the visual studio compiler using that command window.

On Thu, Apr 23, 2009 at 11:28 AM, Rohan Solanki <solanki.rohan@xxxxxxxxx> wrote:

ok thanks.... do v have to change anything in vrsa32.bat in the visualstudio/bin folder to compile wireshark...

On Thu, Apr 23, 2009 at 8:38 PM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:

Rohan Solanki wrote:

yes  i did go to the site ... but there is "Microsoft Server 2003 SDK" .. I did not find "SP2 SDK"...

The SDK name is for the maximum level of OS supported by the headers in the SDK, not the version of the OS you are compiling on.  Other defines in the application will control which OS is actually targeted.

You should be OK with the 2003 SDK.

-- 
Regards,

Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe