Re: Building Epics base 3.15.2 in Windows 7

[Mark Engbretson <engbretson@anl.gov>]

That batch files doesn't set ANY compiler related paths.

On Nov 6, 2015, at 16:08, Mark Rivers <rivers@cars.uchicago.edu> wrote:

I think I may see your problem:

You have the line:
call "C:\Program files (x86)\Microsoft Visual Studio 14.0\Common7\tools\vsvars32.bat"

I have this line:
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86_amd64

Note that your line starts with "call", while mine does not.

I believe that "call" creates a new batch file context.  That means that the definitions in vsvars32.bat are not preserved when the "called" batch file returns.

I think you should delete "call" and just invoke the vsvars32.bat file directly.

Mark

-----Original Message-----
From: Klyachko, Alexander Vitalievich [mailto:aklyachk@indiana.edu] 
Sent: Friday, November 06, 2015 4:00 PM
To: Mark S. Engbretson; Mark Rivers; Andrew Johnson; 'Engbretson, Mark S.'
Cc: tech-talk@aps.anl.gov
Subject: Re: Building Epics base 3.15.2 in Windows 7

That is probably true, but I can't figure out why.  I do have a script which opens a cmd window and sets variables before each make execution. Here's output:

C:\base-3.15.2\startup>rem EPICS base win32-x86 build

C:\base-3.15.2\startup>cd c:\base-3.15.2

c:\base-3.15.2>set EPICS_HOST_ARCH=win32-x86

c:\base-3.15.2>rem set PATH