RE: Fix for building 3.15.4 on windows-x64-static

[Mark Rivers <rivers@cars.uchicago.edu>]

Searching for the presence of "Visual Studio 10.0" in the PATH environment variable might work.  I don't know if the problem exists in versions of Visual Studio earlier than 2010.  Are those supported by EPICS base 3.15.4 anyway?

> Is your fix necessary for SHARED_LIBRARIES=NO or STATIC_BUILD=YES? Or  both, or any?

I believe it is only necessary for SHARED_LIBRARIES=NO.  That was definitely true before I removed the optimization disabling from src/LibCom/calc/calcPerform.c.  I need to test that dynamic builds still work after that change, but I suspect they will.  I will test that today.

Mark

-----Original Message-----
From: core-talk-bounces@aps.anl.gov [mailto:core-talk-bounces@aps.anl.gov] On Behalf Of Ralph Lange
Sent: Thursday, September 08, 2016 9:05 AM
To: 'EPICS core-talk'
Subject: Re: Fix for building 3.15.4 on windows-x64-static

On 08/09/2016 14:49, Mark Rivers wrote:
> 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.


Interesting. I was actually thinking more along the lines of checking 
for the presence of environment variables like %VS120COMNTOOLS% (for VS 
12.0 = 2013) or %VS100COMNTOOLS% (for VS 10.0 = 2010).
Your idea would also get the architecture, but make should know that 
already.
Is your fix necessary for SHARED_LIBRARIES=NO or STATIC_BUILD=YES? Or 
both, or any?

~Ralph