Experimental Physics and Industrial Control System
Thank you Janet.
I understand that the %c:%.stt target needs to be included in the
RULES. This can be done by either editing the ioc Makefile ( as
described below) or editing the EPICS_BASE config(ure?) files.
But I do not want to edit the EPICS_BASE/config(ure) files so I can
easily reinstall epics or duplicate my installation. So to change the
SNCSEQ build variable, I use
export SNCSEQ=/path/to/seq
and then build epics with make -e (environment has precedence on make
variables). This works great.
1/
Obviously I cannot use the same trick to include a file in a makefile
unless the inclusion is function of a make variable.
2/
Now I am building synApps. And for the same reason as with EPICS_BASE, I
do not want to change any Makefile. Unfortunately all of the build that
includes the sequencer (stt, st files) breaks. Of course, there is now
rules to build C files from the stt/st ones.
Does that mean that now I have no choice but to edit one of my
Makefiles?
Shouldn't the EPICS_BASE build system be smart enough to to include a
rule for stt files based on the setting of SNCSEQ?
Any input is appreciated....
--
Emmanuel
On Mon, 2006-10-09 at 11:08 -0500, Janet Anderson wrote:
> If a configure/RULES_BUILD file exists in a support module defined
> in an application's RELEASE file it will be included by Makefiles
> during the build. This allows a support module to create module
> specific build rules to be used by ioc applications which use the
> support module.
>
> When a make is done in the configure directory of a makeBaseApp.pl
> application a RULES_INCLUDE file is created in each O.<arch>
> subdirectory. This file contains an include line for a RULES_BUILD
> file from each support module defined in the configure/RELEASE file
> (except EPICS_BASE). The created RULES_INCLUDE file will be included
> by EPICS_BASE configure files during the build.
>
> Janet
>
> Eric Norum wrote:
> > I'm sure that Janet can provide a better explanation of this, but the
> > sequencer seems to work fine for me without requiring any manual
> > additions to the RULES_BUILD file. I have only to add a definition for
> > SNCSEQ in the configure/RELEASE file:
> >
> > SNCSEQ=/usr/local/iocapps/R3.14.8.2/modules/soft/seq/2-0-11-asd2
> >
> >
> > On Oct 6, 2006, at 8:00 PM, Emmanuel Mayssat wrote:
> >
> >> Mark,
> >>
> >> I also need to include the RULES_BUILD file that comes with the
> >> sequencer source to be able to build the C files from the st one.
> >>
> >>
> >> MyIoc_SRCS=sequencer.st
> >>
> >> include ${EPICS_SEQUENCER_TOP_DIR}/configure/RULES_BUILD
> >>
> >> --
> >> Emmanuel
> >>
> >>
> >>
> >
> > --
> > Eric Norum <[email protected] <mailto:[email protected]>>
> > Advanced Photon Source
> > Argonne National Laboratory
> > (630) 252-4793
> >
> >
>
- Navigate by Date:
- Prev:
Re: CALC record weird behaviour Dirk Zimoch
- Next:
RE: OMS MAXv reset/power-up problem Mark Rivers
- 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:
NSLS Controls Computing Leader Position Zitvogel, Emil
- Next:
firewire video on RTEMS-4.6.x-MVME5500 Kate Feng
- 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