EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024  Index 2002  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: Architecture dependent dbd files
From: Ralph Lange via Core-talk <[email protected]>
To: EPICS Core Talk <[email protected]>
Date: Tue, 5 Nov 2019 11:17:36 +0100
On Mon, 4 Nov 2019 at 22:44, Johnson, Andrew N. via Core-talk <[email protected]> wrote:
On 11/2/19 2:36 PM, Mark Rivers via Core-talk wrote:

This seems silly.  It seems like the right solution is to simply make dbd files be architecture-dependent, rather than a single version in O.Common.

If each target <arch> has its own set of dbd files, it would need its own copies of the generated *Record.h and menu*.h include files to match, and we would have to add new dbd/<arch> and include/arch/<arch> install directories to put them in. The build system would get a bit more complicated to support these, and builds will take a bit longer as each architecture built will have to run the conversion scripts (currently they only get run once, by the first host architecture).

We could generate common dbd/.h files by default, and require explicit configuration of arch-dependent files in the application - which would go into the additional .../<arch> directories.
Still: for that to be transparent to the IOC applications, we would have to require the IOC to have the arch-dependent directories somehow in the search path so that arch-dependency of those files doesn't show in the st.cmd.
And: if dbd files are arch-dependent, the databases themselves are likely to be arch-dependent, too... adding lots of complexity ... can of worms.

Since we have been shortly discussing perspectives for the EPICS build system during the last face-to-face meeting: At some point things would get *a lot* simpler by doing out-of-tree builds and let each target architecture have their own copy of the full installation without any internal .../<arch> directories.

Cheers,
~Ralph
References:
Architecture dependent dbd files Mark Rivers via Core-talk
Re: Architecture dependent dbd files Johnson, Andrew N. via Core-talk
Navigate by Date:
Prev: FW: Circular Mark Rivers via Core-talk
Next: RE: Architecture dependent dbd files Mark Rivers via Core-talk
Index: 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: Architecture dependent dbd files Johnson, Andrew N. via Core-talk
Next: RE: Architecture dependent dbd files Mark Rivers via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 
ANJ, 05 Nov 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·