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: Bug in e2db and "FATAL error"
From: Nick Rees <[email protected]>
To: [email protected]
Date: Thu, 14 Jun 2001 11:29:15 -1000 (HST)
Rozelle,

Good to hear your back in circulation. Thanks for the -if flag tip -
unfortunately, we don't have that version of sch2edif, so we have to live
with the fatal errors.

I have spent a bit of time setting up Capfast lately since we got rid of
some softlinks in our build system and I thought I might share what I have
done to deal schematic dependencies between applications.

Firstly, any dependent symbols and schematics I install into the install
tree of EPICS or the application in the
$(INSTALL_LOCATION)/templates/capfast/sym directory. I also install the
new EPICS menus in $(INSTALL_LOCATION_BASE)/templates/capfast. I chose
templates because that seemed to be the most appropriate directory in the
install tree. It doesn't really matter - it just helps if it is in a
consistent place.

Secondly, I leave the capfast install tree pristine. This should make it
easier if I update Capfast.

Then, for interactive editing I alias the various capfast tools so I can
use them interactively and pick up the correct paths:

alias xschedit 'xschedit ${CAPFAST_SYM_PATH} -k${EPICS_BASE}/templates/capfast+'
alias xsymed   'xsymed   ${CAPFAST_SYM_PATH}'

and so CAPFAST_SYM_PATH becomes very similar to a normal path that you can
add to by, for example:

setenv CAPFAST_SYM_PATH "${CAPFAST_SYM_PATH} -p+/your/app/install/templates/capfast/sym"

I must say it would be nice if Capfast would look at an environment
variable for these paths anyway, but this is a simple workaround.

Finally, I do similar things with the make rules - if I have a dependent
application I can add a new path by adding to SCH2EDIF_SYSFLAGS:

SCH2EDIF_SYSFLAGS += -p+/your/app/install/templates/capfast/sym

This seems to work reasonably well, and allows us to share between
applications with just a few simple rules in the makefiles and lines in
the overall system-wide cshrc and login files.

Cheers,

Nick Rees

Joint Astronomy Centre               Ph:       +1 (808) 961-3756
660 N. Aohoku Place                  Fax:      +1 (808) 961-6516
Hilo, HI.  96720                     Internet: [email protected]



Replies:
R3.13.4 CONFIG.Host.hp700 Jim Thomas
References:
Re: Bug in e2db and "FATAL error" Rozelle Wright

Navigate by Date:
Prev: Re: Bug in e2db and "FATAL error" Rozelle Wright
Next: Instrument driver Jennifer Tobin
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: Bug in e2db and "FATAL error" Rozelle Wright
Next: R3.13.4 CONFIG.Host.hp700 Jim Thomas
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 ·