Hi,
I'm beginning to build our EPICS modules under Windows R3.14.11
(updating from R3.14.10) and I'm running into some problems with
checkRelease in the configure directory.
The way we setup our RELEASE files make use of macro expansion. So for
example the synApps 'std' module we have:
configure\RELEASE:
TEMPLATE_TOP=$(EPICS_BASE)/templates/makeBaseApp/top
WORK=/dls_sw/work/R3.14.11/support
SUPPORT=/dls_sw/prod/R3.14.11/support
SNCSEQ=$(SUPPORT)/seq
ASYN=$(WORK)/asyn
EPICS_BASE=/dls_sw/epics/R3.14.11/base
And for the win32-x86 target we have a RELEASE.win86-x32 which just
override the WORK and SUPPORT macros (saving us a bit of typing and
ensure the same versions of dependencies are consistent across target
platforms):
configure\RELEASE.win86-x32:
TEMPLATE_TOP=$(EPICS_BASE)/templates/makeBaseApp/top
SUPPORT=W:\prod/R3.14.11/support
WORK=W:\work/R3.14.11/support
EPICS_BASE=W:\epics/R3.14.11/base
The problem comes when make builds the configure directory. More
specifically when running the convertRelease.pl checkRelease command:
W:\work\R3.14.11\support\std\configure>mingw32-make
perl W:\epics/R3.14.11/base/bin/win32-x86/makeMakefile.pl O.win32-x86
../..
perl -MExtUtils::Command -e mkpath O.Common
mingw32-make -C O.win32-x86 -f ../Makefile TOP=../.. T_A=win32-x86
install
mingw32-make[1]: Entering directory
`W:/work/R3.14.11/support/std/configure/O.win32-x86'
perl W:\epics/R3.14.11/base/bin/win32-x86/convertRelease.pl checkRelease
/dls_sw/epics/R3.14.11/base: No such file or directory at
W:\epics/R3.14.11/base/bin/win32-x86/convertRelease.pl line 208
mingw32-make[1]: *** [checkRelease] Error 2
mingw32-make[1]: Leaving directory
`W:/work/R3.14.11/support/std/configure/O.win32-x86'
mingw32-make: *** [install.win32-x86] Error 2
The same modules with the same RELEASE files used to build OK on
R3.14.10 - but not anymore.
After playing around with the macros in the RELEASE and
RELEASE.win32-x86 I found that if I don't use the macro expansion (so
delete the WORK= and SUPPORT= macros and put all dependencies with full
paths in both RELEASE files) it works and checkRelease completes. This
leads me to think that the perl scripts (or makefile?) that expand
macros is doing something different from R3.14.10...? However, I have
not been able to trace down any changes in base that seems relevant to
my problem.
If I set the CHECK_RELEASE=NO option, the module build OK but I don't
really want to do that for obvious reasons...
Just for information: We are using the following toolchain:
GNU Make 3.81 from the MinGW package.
ActiveState Perl v5.10.0
Cheers,
Ulrik
--------------------------------------------------------------------
Ulrik Pedersen phone: +44(0)1235-778580
Software Engineer email: [email protected]
Diamond Light Source Ltd.
Rutherford Appleton Laboratory,
Chilton, Didcot
Oxfordshire OX11 0DE
--------------------------------------------------------------------
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- Replies:
- Re: checkRelease on Windows Andrew Johnson
- Navigate by Date:
- Prev:
Re: aiRecord/devGpib problem Andrew Wagner
- Next:
archive server discussion Loris Giovannini
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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: aiRecord/devGpib problem Allison, Stephanie
- Next:
Re: checkRelease on Windows Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|