Experimental Physics and Industrial Control System
Dear all,
Nick Rees wrote (I am responding only to sections which raise questions):
> I have spent the past few days working on this at MPIA. We are
> progressing along largely similar lines so it would be good to come to
> a convergence.
Yes, let's go for a common approach, at least for Keck and UKIRT, but
hopefully also for Gemini and for anyone else who is interested.
> 1. Creating a new application environment called uae, rather than
> trying to maintain backwards compatibility with sae.
uae is fine. I have been using saekeck myself for now.
> 2. Retaining getrel, but the new applSetupDir removes some of the
> history. I was thinking of dropping getrel altogether and putting
> the little remaining in getrel in applSetupDir.
This would be fine. I currently execute getrel from applSetupDir if the
-g option is specified but having a single script seems neater. Having
a script to create and populate a new sub-directory of src would be
useful too. (also, getrel is in base so not using it avoids some path
problems)
> 3. In the src makefile I have a rule called mkdir.% which creates a
> sub-directory called $* (i.e. %) and populates it with Makefiles and
> .cvsignores. This also sets $(EPICS) to $(EPICS)/.. in the subdirectory
> makefiles. This avoids the need to have links to base and
> extensions in every sub-directory. It also concatenates `DIR += <subdir>`
> to a Makefile.Dirs file so the Make's propogate.
I like this (it addresses the desire to have a script to create a new src
sub-directory). The base, config, extensions links are not used by my Makefiles
but are useful for binary paths so I would retain them. They are always to ..
so you propagate up the hierarchy looking for base until you hit the application
directory.
Concatenating DIR to Makefile.Dirs isn't necessarily what you want, but I
guess you can edit it afterwards.
> 4. In the templates directory the templates are of the form:
>
> applMakefile.<dirname>
> applMakefile.Unix.<dirname>
> applMakefile.Vx.<dirname>
> appl.cvsignore.<dirname>
>
> i.e. the db directory Makefile is applMakefile.db
>
> appl.cvsignore.db is created during the build of the extensions
> tree by a sed/awk script which parses dbRecTypes.ascii. There should
> be a make target in the db Makefile which updates this, but I haven't
> got around to this.
>
> The src templates are propagated down the src tree by the mkdir.% rule.
Oh, I see. the db/.cvsignore is to ignore things like *.mbbi. Clever. I
haven't worried about db yet since I hope that most of our databases will
be ASCII .db files generated from .sch files.
I like the model of the template directory having at least some of the
structure of the application directory, but we can talk about this. It
makes for more natural names.
You noted that I have moved db, dl, ar etc to src? Is this acceptable?
There are some issues still to be addressed to do with where you actually
are when you _run_ this stuff and start creating files. I don't think you
should be anywhere near the development tree so in fact it doesn't make much
sense to have the ar sub-directories (except for testing).
William
- Navigate by Date:
- Prev:
links and CVS Alan K Biocca
- Next:
free_gdct. Am I missing a resources file?? 415
- 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: application directories and CVS, GNU make etc Nick Rees
- Next:
Re: application directories and CVS, GNU make etc Marty Kraimer
- 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