Experimental Physics and
Industrial Control System

Mark Rivers <[email protected]> · Thu, 8 Sep 2016 12:49:03 +0000

Running "cl" with no arguments will produce output like this:

*******************************
J:\epics\devel-3.15>cl
Microsoft (R) C/C++ Optimizing Compiler Version 16.00.40219.01 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

*******************************

I think that output could be parsed to determine the compiler version, but I don't know how to do that.  "16.xx.xxxxx.xx for 64" is the string we want to detect for VS 2010.

Mark

________________________________
From: [email protected] [[email protected]] on behalf of Ralph Lange [[email protected]]
Sent: Thursday, September 08, 2016 2:09 AM
To: 'EPICS core-talk'
Subject: Re: Fix for building 3.15.4 on windows-x64-static

Hi Mark,

On 08/09/2016 01:08, Mark Rivers wrote:
I have come up with a better solution for the problem with the Visual Studio 2010 compiler crashes.
[...]
I changed configure/os/CONFIG_SITE.Common.windows-x64-static as follows:
# 64-bit Visual Studio 2010 builds fail when built with the -GL optimization
# flag which is set in CONFIG.win32-x86.win32-x86 with these lines:
# OPT_CFLAGS_YES = -Ox -GL -Oy-
# OPT_CXXFLAGS_YES = -Ox -GL -Oy-
# The lines below have the -GL flag removed from OPT_CFLAGS_YES and OPT_CXXFLAGS_YES.
# If you are using a newer version of Visual Studio you can try removing these lines.
OPT_CFLAGS_YES   = -Ox -Oy-
OPT_CXXFLAGS_YES = -Ox -Oy-

My impression is that VS 2013 and 2015 do not have that issue. (For older versions, I only have access to the Express editions that do not contain 64bit compilers.)

Is there a way to determine the VS version during make, so that we could apply your suggested change only for specific VS versions that need it?

Cheers,
~Ralph

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System