Re: Windows build problems now seem solved ... but a small update to the build doc might help

[Richard Sharpe <realrichardsharpe () gmail com>]

On Sun, Feb 1, 2015 at 2:36 AM, Graham Bloice
<graham.bloice () trihedral com> wrote:
> 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.

Well, in retrospect it was obvious, just not obvious to someone new at
that stuff.

Where is the doc, btw?

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___________________________________________________________________________
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