EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: src/ reorganization
From: "Davidsaver, Michael" <[email protected]>
To: "Andrew Johnson" <[email protected]>, <[email protected]>
Date: Fri, 10 Dec 2010 16:19:12 -0500

> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> ...
> > If there aren't major changes then next week I will create a branch
> with
> > these changes and request a merge.
> >
> > The first stage will look like:
> > > == Full list of renames
> > >
> > > tools      = tools
> > > libCom     = libCom
> > > toolsComm  = libCom/tools
> > > RTEMS      = libCom/RTEMS
> > > as         = ioc/as
> > > bpt        = ioc/bpt
> > > db         = ioc/db
> > > dbStatic   = ioc/dbStatic
> > > dbtools    = ioc/dbtemplate
> > > misc       = ioc/misc
> > > registry   = ioc/registry
> > > rsrv       = ioc/rsrv
> > > dev/softDev= std/dev
> > > dev/testDev= std/test
> > > rec        = std/rec
> > > softIoc    = std/softIoc
> > > ca         = ca/client
> > > cap5       = ca/client/perl
> > > catools    = ca/client/tools
> > > cas        = ca/legacy/pcas
> > > excas      = ca/legacy/pcas/ex
> > > gdd        = ca/legacy/gdd
> > > makeBaseApp= template/base
> > > makeBaseExt= template/ext
> > > util       = util
> 
> One question about the layout: I'm wondering whether in the final
> structure
> individual directories should either be a branch node or a leaf node,
> i.e.
> they should either contain sub-directories and a Makefile, or they
> contain
> source files and a Makefile, but never both.  Your ca/client and
> ca/legacy/pcas directories are currently mixed nodes.

Trying to adhere to this is what lead to present lib*Ioc situation.  I
would rather start with what I want the result of the build to be, how I
want the code to be organized, and then adapt the build system to
produce it.

> Was your intention to follow the libCom model for source directories?

Yes.  For the ioc/ and std/ directories at least.

> My
> worry is that the libCom/Makefile is unwieldy because it has to name
> all of
> the files in the different sub-directories.

As long as the EPICS build system forces the distinction between
branch/leaf node we will have this problem.  

The Makefiles will be large, but there will be fewer of them.  Basically
all of my dislike of the current build system come from the "evil"
include statement, and having to hunt to find anything.  It may be a
personal preference, but in the src/ directory at least I would rather
have a few large Makefiles.


Michael



Replies:
Re: src/ reorganization Andrew Johnson
RE: src/ reorganization Davidsaver, Michael
References:
src/ reorganization Davidsaver, Michael
RE: src/ reorganization Davidsaver, Michael
Re: src/ reorganization Andrew Johnson

Navigate by Date:
Prev: Re: src/ reorganization Andrew Johnson
Next: Re: src/ reorganization Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: src/ reorganization Andrew Johnson
Next: Re: src/ reorganization Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·