Re: [Wireshark-dev] Now problems packaging ...

2015-01-31 Thread Richard Sharpe
On Sat, Jan 31, 2015 at 2:39 PM, Richard Sharpe
 wrote:
> Hi folks,
>
> So, my build completed OK. However, when I attempted the packaging step I got:
>
> --
> Processing config: c:\Program Files (x86)\NSIS\nsisconf.nsh
> Processing script file: "wireshark.nsi" (ACP)
> File: "c:\Users\rjsharpe\Wireshark\Wireshark-win64-libs\vcredist_x64.exe" -> 
> no
> files found.
> Usage: File [/nonfatal] [/a] ([/r] [/x filespec [...]] filespec [...] |
>/oname=outfile one_file_only)
> Error in script "wireshark.nsi" on line 349 -- aborting creation process
> NMAKE : fatal error U1077: '"\Program Files (x86)\NSIS\makensis.exe"' : 
> return c
> ode '0x1'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 
> 12.0
> \VC\BIN\amd64\nmake.exe"' : return code '0x2'
> Stop.
> 
>
> Any hints here?

A quick application of the vcredist_x64 tonic seems to have fixed this problem.

The doc needs another update.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Now problems packaging ...

2015-01-31 Thread Richard Sharpe
Hi folks,

So, my build completed OK. However, when I attempted the packaging step I got:

--
Processing config: c:\Program Files (x86)\NSIS\nsisconf.nsh
Processing script file: "wireshark.nsi" (ACP)
File: "c:\Users\rjsharpe\Wireshark\Wireshark-win64-libs\vcredist_x64.exe" -> no
files found.
Usage: File [/nonfatal] [/a] ([/r] [/x filespec [...]] filespec [...] |
   /oname=outfile one_file_only)
Error in script "wireshark.nsi" on line 349 -- aborting creation process
NMAKE : fatal error U1077: '"\Program Files (x86)\NSIS\makensis.exe"' : return c
ode '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0
\VC\BIN\amd64\nmake.exe"' : return code '0x2'
Stop.


Any hints here?

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Windows build problems now seem solved ... but a small update to the build doc might help

2015-01-31 Thread Richard Sharpe
Hi folks,

It seems that my real problem was that I had not paid careful
attention to this statement in the guide:

"From the Start Menu (or Start Screen), navigate to the Visual Studio
2013 → Visual Studio Tools directory and choose the Command Prompt
appropriate for the build you wish to make, e.g. VS2013 x86 Native
Tools Command Prompt for a 32 bit version."

There are several command prompts with VS2013, and the one I wanted
was the VS2013 x64 Native Tools Command Prompt.

Perhaps that statement above could be modified to add another entry
after the eg and in clude:, VS2013 x64 Native Tools Command Prompt for
an x64 version.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Building wireshark on Win7 gives me the error about win32.mak not found

2015-01-31 Thread Richard Sharpe
On Sat, Jan 31, 2015 at 1:47 PM, Richard Sharpe
 wrote:
> On Sat, Jan 31, 2015 at 1:07 PM, Richard Sharpe
>  wrote:
>> On Sat, Jan 31, 2015 at 12:55 PM, Richard Sharpe
>>  wrote:
>>> On Sat, Jan 31, 2015 at 12:50 PM, Richard Sharpe
>>>  wrote:
 On Sat, Jan 31, 2015 at 12:18 PM, Graham Bloice
  wrote:
> On 31 January 2015 at 19:27, Richard Sharpe 
> wrote:
>>
>> Hi folks,
>>
>> I am following the steps at this website:
>>
>> https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
>>
>> and I get this error:
>>
>> c:\Users\blah-blah\Wireshark>nmake -f Makefile.nmake verify_tools
>>
>> Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
>> Copyright (C) Microsoft Corporation.  All rights reserved.
>>
>> Makefile.nmake(8) : fatal error U1052: file 'win32.mak' not found
>> Stop.
>>
>> These appear to be in the environment:
>>
>> CYGWIN=nodosfilewarning
>> QT5_BASE_DIR=C:\Qt\5.4\msvc2013_64_opengl
>> VisualStudioVersion=12.0
>> WIRESHARK_BASE_DIR=c:\Users\rjsharpe\Wireshark
>> WIRESHARK_TARGET_PLATFORM=win64
>> WIRESHARK_VERSION_EXTRA=-RJS
>>
>> What else do I need to do?
>>
>>
>
> See this thread
> (https://www.wireshark.org/lists/wireshark-dev/201501/msg00026.html) about
> windows build instructions.
>
> MS has dropped the file from the SDK for 8.x, so you have to copy the file
> from a 7.x SDK which should have been installed along with VS2013.
>
> I seem to have not completed the task of updating the build instructions.

 OK, but copy it to where? To the 8.x SDK?
>>>
>>> Copying it to the wireshark directory was enough. Maybe I did this a
>>> year ago and forgot and then when I did a git clean -fxd I blew it
>>> away :-(
>>
>> OK, after copying it to wsutil as well, I now get this:
>>
>> 
>> file_util.obj : fatal error LNK1112: module machine type 'X86' conflicts 
>> with ta
>> rget machine type 'x64'
>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 
>> 12.0
>> \VC\BIN\link.EXE"' : return code '0x458'
>> Stop.
>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 
>> 12.0
>> \VC\BIN\nmake.exe"' : return code '0x2'
>> Stop.
>> --
>>
>> Investigating.
>
> Figured this one out. I had tried running vcvarsall to solve the
> problem earlier and it sets up some defaults for x86 rather than x64
> binaries.

I thought I was doing well until this hit:

--
Linking Wireshark-gtk.exe
link @C:\Users\rjsharpe\AppData\Local\Temp\nm5D77.tmp
libgtkui.lib(main.obj) : error LNK2019: unresolved external symbol codec_registe
r_plugin_types referenced in function main
libgtkui.lib(main.obj) : error LNK2019: unresolved external symbol register_all_
codecs referenced in function main
libgtkui.lib(rtp_player.obj) : error LNK2019: unresolved external symbol find_co
dec referenced in function decode_rtp_packet
libgtkui.lib(rtp_player.obj) : error LNK2019: unresolved external symbol codec_i
nit referenced in function decode_rtp_packet
libgtkui.lib(rtp_player.obj) : error LNK2019: unresolved external symbol codec_r
elease referenced in function rtp_decoder_value_destroy
libgtkui.lib(rtp_player.obj) : error LNK2019: unresolved external symbol codec_g
et_channels referenced in function decode_rtp_packet
libgtkui.lib(rtp_player.obj) : error LNK2019: unresolved external symbol codec_g
et_frequency referenced in function decode_rtp_packet
libgtkui.lib(rtp_player.obj) : error LNK2019: unresolved external symbol codec_d
ecode referenced in function decode_rtp_packet
Wireshark-gtk.exe : fatal error LNK1120: 8 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0
\VC\BIN\amd64\link.EXE"' : return code '0x460'
Stop.
-

Is there some library missing?

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] How to call a sub-dissector many times without knowing the exact data size

2015-01-31 Thread Guy Harris

On Jan 31, 2015, at 1:46 PM, wsgd  wrote:

> I want to call a sub-dissector many times. 
> I know the total size of my data. 
> I do NOT know the size to give to the sub-dissector. 
> The sub-dissector will know (by itself) the size to dissect. 
> 
> The corresponding scheme from the parent dissector point of view : 
> 
> |---Packet data (total size is 
> known)| 
> |--Parent dissector--|--sub-dissector 1 (size is 
> unknown)--|...|--sub-dissector N (size is unknown)--| 
> 
> 
> The sub-dissector will be called by dissector_try_uint (or call_dissector or 
> eventually dissector_try_heuristic). 
> 
> 
> Question 1) 
> Is it possible to call dissector_try_uint (or ...) with more data than needed 
> by the sub-dissector ? 

Yes.

> Question 2) 
> How to know how many bytes have been dissected by the sub-dissector ? 

Have the sub-dissector be a "new-style" dissector, which is expected to return 
the number of bytes of data that it dissected.

For "old-style" dissectors, which do not return a value, the dissector-calling 
mechanism will return tvb_captured_length(), so it appears as if the entire 
tvbuff handed to it was dissected.

dissector_try_uint(), call_dissector(), etc. return the return value of a 
new-style dissector or the tvbuff captured length of an old-style dissector.

Note that a new-style dissector can return 0, which is assumed to mean "this 
isn't a packet for my protocol".

This does *not* work for heuristic dissectors.  Perhaps heuristic dissectors 
could be changed to return a bytes-dissected value rather than a Boolean, with 
0 meaning "I dissected nothing because this isn't a packet for my protocol"; I 
think there were cases for non-heuristic dissectors where nothing is dissected 
but the dissection was valid, e.g. an RPC-like protocol where a reply has no 
data at the RPC layer but has data at the layer of the particular RPC protocol 
being used, and I think I discovered that when trying to make all dissectors 
new-style dissectors, but I can't remember what I found.

For a heuristic dissector, however, the dissector has to look at *some* data in 
order to determine whether the packet is for its protocol or not, so presumably 
it could never return 0 if the packet is for its protocol.
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] Building wireshark on Win7 gives me the error about win32.mak not found

2015-01-31 Thread Richard Sharpe
On Sat, Jan 31, 2015 at 1:07 PM, Richard Sharpe
 wrote:
> On Sat, Jan 31, 2015 at 12:55 PM, Richard Sharpe
>  wrote:
>> On Sat, Jan 31, 2015 at 12:50 PM, Richard Sharpe
>>  wrote:
>>> On Sat, Jan 31, 2015 at 12:18 PM, Graham Bloice
>>>  wrote:
 On 31 January 2015 at 19:27, Richard Sharpe 
 wrote:
>
> Hi folks,
>
> I am following the steps at this website:
>
> https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
>
> and I get this error:
>
> c:\Users\blah-blah\Wireshark>nmake -f Makefile.nmake verify_tools
>
> Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> Makefile.nmake(8) : fatal error U1052: file 'win32.mak' not found
> Stop.
>
> These appear to be in the environment:
>
> CYGWIN=nodosfilewarning
> QT5_BASE_DIR=C:\Qt\5.4\msvc2013_64_opengl
> VisualStudioVersion=12.0
> WIRESHARK_BASE_DIR=c:\Users\rjsharpe\Wireshark
> WIRESHARK_TARGET_PLATFORM=win64
> WIRESHARK_VERSION_EXTRA=-RJS
>
> What else do I need to do?
>
>

 See this thread
 (https://www.wireshark.org/lists/wireshark-dev/201501/msg00026.html) about
 windows build instructions.

 MS has dropped the file from the SDK for 8.x, so you have to copy the file
 from a 7.x SDK which should have been installed along with VS2013.

 I seem to have not completed the task of updating the build instructions.
>>>
>>> OK, but copy it to where? To the 8.x SDK?
>>
>> Copying it to the wireshark directory was enough. Maybe I did this a
>> year ago and forgot and then when I did a git clean -fxd I blew it
>> away :-(
>
> OK, after copying it to wsutil as well, I now get this:
>
> 
> file_util.obj : fatal error LNK1112: module machine type 'X86' conflicts with 
> ta
> rget machine type 'x64'
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 
> 12.0
> \VC\BIN\link.EXE"' : return code '0x458'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 
> 12.0
> \VC\BIN\nmake.exe"' : return code '0x2'
> Stop.
> --
>
> Investigating.

Figured this one out. I had tried running vcvarsall to solve the
problem earlier and it sets up some defaults for x86 rather than x64
binaries.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] How to call a sub-dissector many times without knowing the exact data size

2015-01-31 Thread wsgd

Hello,


I want to call a sub-dissector many times.
I know the total size of my data.
I do NOT know the size to give to the sub-dissector.
The sub-dissector will know (by itself) the size to dissect.

The corresponding scheme from the parent dissector point of view :

|---Packet data (total size is 
known)|
|--Parent dissector--|--sub-dissector 1 (size is 
unknown)--|...|--sub-dissector N (size is unknown)--|



The sub-dissector will be called by dissector_try_uint (or 
call_dissector or eventually dissector_try_heuristic).



Question 1)
Is it possible to call dissector_try_uint (or ...) with more data than 
needed by the sub-dissector ?

It seems not a problem.

Question 2)
How to know how many bytes have been dissected by the sub-dissector ?



Regards,
Olivier

--
Wireshark Generic Dissectorhttp://wsgd.free.fr

___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Building wireshark on Win7 gives me the error about win32.mak not found

2015-01-31 Thread Richard Sharpe
On Sat, Jan 31, 2015 at 12:55 PM, Richard Sharpe
 wrote:
> On Sat, Jan 31, 2015 at 12:50 PM, Richard Sharpe
>  wrote:
>> On Sat, Jan 31, 2015 at 12:18 PM, Graham Bloice
>>  wrote:
>>> On 31 January 2015 at 19:27, Richard Sharpe 
>>> wrote:

 Hi folks,

 I am following the steps at this website:

 https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html

 and I get this error:

 c:\Users\blah-blah\Wireshark>nmake -f Makefile.nmake verify_tools

 Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
 Copyright (C) Microsoft Corporation.  All rights reserved.

 Makefile.nmake(8) : fatal error U1052: file 'win32.mak' not found
 Stop.

 These appear to be in the environment:

 CYGWIN=nodosfilewarning
 QT5_BASE_DIR=C:\Qt\5.4\msvc2013_64_opengl
 VisualStudioVersion=12.0
 WIRESHARK_BASE_DIR=c:\Users\rjsharpe\Wireshark
 WIRESHARK_TARGET_PLATFORM=win64
 WIRESHARK_VERSION_EXTRA=-RJS

 What else do I need to do?


>>>
>>> See this thread
>>> (https://www.wireshark.org/lists/wireshark-dev/201501/msg00026.html) about
>>> windows build instructions.
>>>
>>> MS has dropped the file from the SDK for 8.x, so you have to copy the file
>>> from a 7.x SDK which should have been installed along with VS2013.
>>>
>>> I seem to have not completed the task of updating the build instructions.
>>
>> OK, but copy it to where? To the 8.x SDK?
>
> Copying it to the wireshark directory was enough. Maybe I did this a
> year ago and forgot and then when I did a git clean -fxd I blew it
> away :-(

OK, after copying it to wsutil as well, I now get this:


file_util.obj : fatal error LNK1112: module machine type 'X86' conflicts with ta
rget machine type 'x64'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0
\VC\BIN\link.EXE"' : return code '0x458'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0
\VC\BIN\nmake.exe"' : return code '0x2'
Stop.
--

Investigating.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Building wireshark on Win7 gives me the error about win32.mak not found

2015-01-31 Thread Richard Sharpe
On Sat, Jan 31, 2015 at 12:50 PM, Richard Sharpe
 wrote:
> On Sat, Jan 31, 2015 at 12:18 PM, Graham Bloice
>  wrote:
>> On 31 January 2015 at 19:27, Richard Sharpe 
>> wrote:
>>>
>>> Hi folks,
>>>
>>> I am following the steps at this website:
>>>
>>> https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
>>>
>>> and I get this error:
>>>
>>> c:\Users\blah-blah\Wireshark>nmake -f Makefile.nmake verify_tools
>>>
>>> Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
>>> Copyright (C) Microsoft Corporation.  All rights reserved.
>>>
>>> Makefile.nmake(8) : fatal error U1052: file 'win32.mak' not found
>>> Stop.
>>>
>>> These appear to be in the environment:
>>>
>>> CYGWIN=nodosfilewarning
>>> QT5_BASE_DIR=C:\Qt\5.4\msvc2013_64_opengl
>>> VisualStudioVersion=12.0
>>> WIRESHARK_BASE_DIR=c:\Users\rjsharpe\Wireshark
>>> WIRESHARK_TARGET_PLATFORM=win64
>>> WIRESHARK_VERSION_EXTRA=-RJS
>>>
>>> What else do I need to do?
>>>
>>>
>>
>> See this thread
>> (https://www.wireshark.org/lists/wireshark-dev/201501/msg00026.html) about
>> windows build instructions.
>>
>> MS has dropped the file from the SDK for 8.x, so you have to copy the file
>> from a 7.x SDK which should have been installed along with VS2013.
>>
>> I seem to have not completed the task of updating the build instructions.
>
> OK, but copy it to where? To the 8.x SDK?

Copying it to the wireshark directory was enough. Maybe I did this a
year ago and forgot and then when I did a git clean -fxd I blew it
away :-(

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Building wireshark on Win7 gives me the error about win32.mak not found

2015-01-31 Thread Richard Sharpe
On Sat, Jan 31, 2015 at 12:18 PM, Graham Bloice
 wrote:
> On 31 January 2015 at 19:27, Richard Sharpe 
> wrote:
>>
>> Hi folks,
>>
>> I am following the steps at this website:
>>
>> https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
>>
>> and I get this error:
>>
>> c:\Users\blah-blah\Wireshark>nmake -f Makefile.nmake verify_tools
>>
>> Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
>> Copyright (C) Microsoft Corporation.  All rights reserved.
>>
>> Makefile.nmake(8) : fatal error U1052: file 'win32.mak' not found
>> Stop.
>>
>> These appear to be in the environment:
>>
>> CYGWIN=nodosfilewarning
>> QT5_BASE_DIR=C:\Qt\5.4\msvc2013_64_opengl
>> VisualStudioVersion=12.0
>> WIRESHARK_BASE_DIR=c:\Users\rjsharpe\Wireshark
>> WIRESHARK_TARGET_PLATFORM=win64
>> WIRESHARK_VERSION_EXTRA=-RJS
>>
>> What else do I need to do?
>>
>>
>
> See this thread
> (https://www.wireshark.org/lists/wireshark-dev/201501/msg00026.html) about
> windows build instructions.
>
> MS has dropped the file from the SDK for 8.x, so you have to copy the file
> from a 7.x SDK which should have been installed along with VS2013.
>
> I seem to have not completed the task of updating the build instructions.

OK, but copy it to where? To the 8.x SDK?

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Building wireshark on Win7 gives me the error about win32.mak not found

2015-01-31 Thread Graham Bloice
On 31 January 2015 at 19:27, Richard Sharpe 
wrote:

> Hi folks,
>
> I am following the steps at this website:
>
> https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
>
> and I get this error:
>
> c:\Users\blah-blah\Wireshark>nmake -f Makefile.nmake verify_tools
>
> Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> Makefile.nmake(8) : fatal error U1052: file 'win32.mak' not found
> Stop.
>
> These appear to be in the environment:
>
> CYGWIN=nodosfilewarning
> QT5_BASE_DIR=C:\Qt\5.4\msvc2013_64_opengl
> VisualStudioVersion=12.0
> WIRESHARK_BASE_DIR=c:\Users\rjsharpe\Wireshark
> WIRESHARK_TARGET_PLATFORM=win64
> WIRESHARK_VERSION_EXTRA=-RJS
>
> What else do I need to do?
>
>
>
See this thread (
https://www.wireshark.org/lists/wireshark-dev/201501/msg00026.html) about
windows build instructions.

MS has dropped the file from the SDK for 8.x, so you have to copy the file
from a 7.x SDK which should have been installed along with VS2013.

I seem to have not completed the task of updating the build instructions.

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Building wireshark on Win7 gives me the error about win32.mak not found

2015-01-31 Thread Richard Sharpe
Hi folks,

I am following the steps at this website:

https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html

and I get this error:

c:\Users\blah-blah\Wireshark>nmake -f Makefile.nmake verify_tools

Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
Copyright (C) Microsoft Corporation.  All rights reserved.

Makefile.nmake(8) : fatal error U1052: file 'win32.mak' not found
Stop.

These appear to be in the environment:

CYGWIN=nodosfilewarning
QT5_BASE_DIR=C:\Qt\5.4\msvc2013_64_opengl
VisualStudioVersion=12.0
WIRESHARK_BASE_DIR=c:\Users\rjsharpe\Wireshark
WIRESHARK_TARGET_PLATFORM=win64
WIRESHARK_VERSION_EXTRA=-RJS

What else do I need to do?

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe