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: Ralph Lange <[email protected]>
To: Rozelle Wright <[email protected]>, [email protected]
Cc: [email protected]
Date: Tue, 3 Apr 2001 17:10:26 -0500 (CDT)
Andy,

I just checked the CVS: the change you are referring to was introduced
to RULES.Host in September 1997, between 3.13.0.beta11 and beta12, so
please excuse us if we don't instantly remember all the details...

Rozelle is right: at that time all the database generation rules were
shifted into a local $TOP/config/RULES.Db file that had additional
features over the "standard" rules in base. The document that Rozelle
pointed you to describes the details. Any newly generated application
would of course contain these rules.

At that point the "standard" rules in base were cleaned up, which led to
the $(DEPSCHS) dependency being thrown out of RULES.Host - a change that
probably only shows up when converting old applications without creating
a new $TOP with the new rules.

Please note also that at the APS, where the Makefile system development
is done, CapFast is not used. At BESSY, where the DB rules originate
from, CapFast is used, but without hierarchical structures. At LANL
hierarchical CapFast schematics are used, but not with $(DEPSCHS).

IMHO the best way to handle the hierarchical CapFast drawings would be
writing a perl script that analyzes the schematics files and extracts
the dependencies into a file that can be included by the Makefile ...
whoever speaks the .sch language well enough may volunteer for that.

Until then, use a local RULES.Db that still has the $(DEPSCHS).

Hope this helps,
Ralph


Replies:
Re: Capfast Rules in 3.13.4 RULES.Host Brian Bevins
References:
Re: Capfast Rules in 3.13.4 RULES.Host Rozelle Wright

Navigate by Date:
Prev: Re: Capfast Rules in 3.13.4 RULES.Host Rozelle Wright
Next: [no subject] Mohan Ramanathan
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: Re: Capfast Rules in 3.13.4 RULES.Host Rozelle Wright
Next: Re: Capfast Rules in 3.13.4 RULES.Host Brian Bevins
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 ·