Re: Building with Visual Studio Professional 2013 ...

["RobiOneKenobi" <robionekenobi () bluewin ch>]

Hi,

You will have to copy the one existing in 

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include\Win32.Mak

Into 

C:\Program Files (x86)\Windows Kits-8.0\Include\um\Win32.Mak
Or
C:\Program Files (x86)\Windows Kits-8.1\Include\um\Win32.Mak

Regards
RobiOneKenobi

-----Original Message-----
From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Richard Sharpe
Sent: Sunday, April 27, 2014 9:49 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Building with Visual Studio Professional 2013 ...

On Sun, Apr 27, 2014 at 12:38 PM, Pascal Quantin
<pascal.quantin () gmail com> wrote:
> 2014-04-27 21:27 GMT+02:00 Pascal Quantin <pascal.quantin () gmail com>:
>
> > Le 27/04/2014 21:18, Richard Sharpe a écrit :
> > > On Sun, Apr 27, 2014 at 11:11 AM, Pascal Quantin
> > > <pascal.quantin () gmail com> wrote:
> > > > Le 27/04/2014 20:02, Richard Sharpe a écrit :
> > > > > Hi folks,
> > > > >
> > > > > It seems like I need to set the MSVC_VARIANT to MSVC2010 as the first
> > > > > invocation of the compiler complains:
> > > > >
> > > > > "_MSC_VER is:1600 but required is:1800"
> > > > >
> > > > > This is after I set MSVC_VARIANT to MSVC2013
> > > > Hi,
> > > >
> > > > looks like you are still using vcvarsall.bat coming from MSVC2010
> > > > (_MSC_VER is defined by the compiler).
> > > Well, this is what I have before anything else:
> > >
> > >    call "c:\Program Files (x86)\Microsoft Visual Studio
> > > 12.0\VC\vcvarsall.bat"
> > >
> > > and this is what happens in the x64 path:
> > >
> > >    :x64
> > >    echo Adding things to the path...
> > >    set PATH=%PATH%;c:\cygwin64\bin
> > >    set WIRESHARK_TARGET_PLATFORM=win64
> > >    call "c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd"
> > > /Release /x64
> > >    title Command Prompt (VC++ 2013 x64)
> > >    goto :eof
> > >
> > > And I did download and install Visual Studio Professional 2013.
> > >
> > > However, it seems that I have these three directories and they were
> > > created/updated by the install:
> > >
> > >    04/27/2014  10:42 AM    <DIR>          Microsoft Visual Studio 10.0
> > >    04/27/2014  08:19 AM    <DIR>          Microsoft Visual Studio 11.0
> > >    04/27/2014  10:55 AM    <DIR>          Microsoft Visual Studio 12.0
> >
> > If I'm not mistaken the SDK 7.1 contains the MSVC2010 compilers, not the
> > MSVC2013 ones
>
>
> MSVC2013 comes with a x64 compiler so you should directly call vcvarsall.bat
> with the x64 parameter, and not call SetEnv.Cmd from the 7.1 SDK.

Ahhh, that sounds reasonable. I got past the original problem, but
then ran into a problem where SetEnv.Cmd was overriding the INCLUDE
path to something that did not exist.

Hmmm, but then I run into problems where win32.mak is not found.

-- 
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

___________________________________________________________________________
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