On 22 July 2013 23:24, Joerg Mayer 
<[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>
 wrote:

On Mon, Jul 22, 2013 at 11:22:38AM +0100, Graham Bloice wrote:

>> Now that OSX appears to be mostly sorted,  Windows could do with some

>> attention, maybe another thread for that, or pick up on the older one.

>> I'm stuck in the same area as this but much worse though, the compiler

>> flags are way out.

>>I spent a few hours today trying to get a development environment working on 
>>a win7 machine. I followed 
>>http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html

>>and managed to install Visual-C++. But the next step already fails for me 
>>(installing the Windows SDK for Windows 7). Everything I've tried failed 
>>during the preparation phase. "view log" does not contain anything that would 
>>help me to understand the problem and the pointers to the website with help 
>>don't help the least.



>>Fresh out of ideas.



>Are you using the web installer or from the iso - 
>http://www.microsoft.com/en-us/download/details.aspx?id=8442



>If you haven't already give the iso a try.



>Graham



>In what way does it fail?



>Regards

>Anders



Hi Joerg,

My colleague had the same issue and was finally able to get it to work as 
follows:

1. UNinstalled 'Visual-C++ 2010' and 'Windows SDK for Windows 7'

2. Reinstalled 'Visual-C++ 2010'

3. Installed 'Microsoft Visual C++ 2010 Express - ENU Service Pack 1 (KB983509)'


This will provide you with a 32-bit build environment.  I haven't tried setting 
up for 64-bit builds yet but I plan to follow 
http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html exactly and 
cross my fingers.

Cal

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to