Subject: |
Re: Fix for building 3.15.4 on windows-x64-static |
From: |
Ralph Lange <[email protected]> |
To: |
"'EPICS core-talk'" <[email protected]> |
Date: |
Thu, 8 Sep 2016 16:05:20 +0200 |
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
- Replies:
- RE: Fix for building 3.15.4 on windows-x64-static Mark Rivers
- References:
- Fix for building 3.15.4 on windows-x64-static Mark Rivers
- RE: Fix for building 3.15.4 on windows-x64-static Mark Rivers
- Re: Fix for building 3.15.4 on windows-x64-static Ralph Lange
- RE: Fix for building 3.15.4 on windows-x64-static Mark Rivers
- Navigate by Date:
- Prev:
RE: Fix for building 3.15.4 on windows-x64-static Mark Rivers
- Next:
RE: Fix for building 3.15.4 on windows-x64-static Mark Rivers
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
- Navigate by Thread:
- Prev:
RE: Fix for building 3.15.4 on windows-x64-static Mark Rivers
- Next:
RE: Fix for building 3.15.4 on windows-x64-static Mark Rivers
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
|