EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Capfast Rules in 3.13.4 RULES.Host
From: Rozelle Wright <[email protected]>
To: [email protected], [email protected]
Date: Tue, 3 Apr 2001 15:11:54 -0600 (MDT)
Hi Andy,

The rules haven't changed if you use the makeBaseApp.pl method of creating
application areas as described in the document 
"EPICS IOC Applications Building and Source Release Control" 
http://www.aps.anl.gov/asd/controls/epics/EpicsDocumentation/AppDevManuals/iocAppBuildSRcontrol3_13_0beta12.html

You have your own config directory with a RULES.Db file containing the line:
%.edf:: ../%.sch $(DEPSCHS)
        @if [ ! -f cad.rc -a -r ../cad.rc ] ; then ln -s ../cad.rc ; fi
        $(SCH2EDIF) $(SCH2EDIF_SYSFLAGS) $(SCH2EDIF_FLAGS) $<

However,  even with $(DEPSCHS) I have always had to touch the 
top level schematic to make the schematics rebuild.  I think DEPSCHS must
need to be defined somehow and I haven't learned how to use it. 
When I change or touch my top schematic the database builds fine
without the $(DEPSCHS).

I believe Thomas Birke may know how RULES.Db is supposed to work to
get schematics to rebuild when any of the underlying schematics have changed.

Rozelle
> From [email protected] Tue Apr  3 06:56 MDT 2001
> Date: Tue, 03 Apr 2001 13:53:27 +0000
> MIME-Version: 1.0
> To: EPICS Questions <[email protected]>
> Subject: Capfast Rules in 3.13.4 RULES.Host
> Content-Transfer-Encoding: 7bit
> 
> Dear All,
> 
> In the config files for 3.13.4, is this a deliberate change 
> in going from RULES.Unix to RULES.Host?
> 
> RULES.Unix
> %.edf: ../%.sch $(DEPSCHS)
>         @if [ ! -f cad.rc -a -r ../cad.rc ] ; then ln -s ../cad.rc ; fi
>         $(SCH2EDIF) $(SCH2EDIF_SYSFLAGS) $(SCH2EDIF_FLAGS) $<
> 
> 
> RULES.Host
> %.edf: ../%.sch
>         @if [ ! -f cad.rc -a -r ../cad.rc ] ; then ln -s ../cad.rc ; fi
>         $(SCH2EDIF) $(SCH2EDIF_SYSFLAGS) $(SCH2EDIF_FLAGS) $<
> 
> I noticed that my top-level schematic never got rebuilt without
> the $(DEPSCHS) dependency.
> 
> Cheers,
> 
> Andy
> 
> -- 
> Observatory Sciences Limited		Email: [email protected]
> William James House			Tel:  44 - (0)1223 - 508257
> Cowley Road			Fax: 44 - (0)1223 - 508258
> Cambridge, CB4 0WX, UK		http://www.observatorysciences.co.uk
> 


Replies:
Re: Capfast Rules in 3.13.4 RULES.Host Ralph Lange

Navigate by Date:
Prev: Linux version CapFast Dr. Chong Lee
Next: Re: Capfast Rules in 3.13.4 RULES.Host Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  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: Capfast Rules in 3.13.4 RULES.Host Andy Foster
Next: Re: Capfast Rules in 3.13.4 RULES.Host Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·