On 12/08/2017 01:57 PM, Mark Rivers wrote:
> I forget exactly what CALL does, but I don't think it's necessary. It's
> worth trying I guess.
Yes, that fixed it. Jenkins runs build commands inside its own .BAT
file, and apparently executing one .BAT file inside another stops the
parent script. It's currently compiling using
> Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24215.1 for x64
as against
> Microsoft (R) C/C++ Optimizing Compiler Version 16.00.40219.01 for x64
> Can you try the command interactively on that machine?
I can't open a command window with the Jenkins build environment, the
Jenkins agent sets up the shell environment by itself, and it's
complicated by the fact that it's all running inside a JVM too.
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- Replies:
- Re: moving initHooks into libCom Andrew Johnson
- References:
- moving initHooks into libCom Michael Davidsaver
- Re: moving initHooks into libCom Andrew Johnson
- Re: moving initHooks into libCom Michael Davidsaver
- Re: moving initHooks into libCom Andrew Johnson
- RE: moving initHooks into libCom Mark Rivers
- Re: moving initHooks into libCom Andrew Johnson
- RE: moving initHooks into libCom Mark Rivers
- Navigate by Date:
- Prev:
RE: moving initHooks into libCom Mark Rivers
- Next:
Build failed in Jenkins: epics-master-windows » DLL,win64 #22 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: moving initHooks into libCom Mark Rivers
- Next:
Re: moving initHooks into libCom Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|