Wireshark mailing list archives
Re: Windows build problems now seem solved ... but a small update to the build doc might help
From: Graham Bloice <graham.bloice () trihedral com>
Date: Sun, 1 Feb 2015 10:36:05 +0000
On 31 January 2015 at 22:31, Richard Sharpe <realrichardsharpe () gmail com> wrote:
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.
I thought it was somewhat obvious, but feel free to amend. -- Graham Bloice
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Windows build problems now seem solved ... but a small update to the build doc might help Graham Bloice (Feb 01)
- Re: Windows build problems now seem solved ... but a small update to the build doc might help Richard Sharpe (Feb 01)