EPICS Re: Building for more than one host architecture

Experimental Physics and Industrial Control System

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	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
<== Date ==>		<== Thread ==>

Subject:	Re: Building for more than one host architecture
From:	[email protected] (Marty Kraimer)
To:	tech-talk@phoebus
Date:	Fri, 16 Jun 1995 07:31:49 -0500

> From [email protected] Thu Jun 15 21:26 CDT 1995
> Date: Thu, 15 Jun 95 19:26:50 PDT
> From: [email protected] (Michael Bordua)
> To: [email protected], [email protected]
> Subject: Re: Building for more than one host architecture
> Content-Type> : > text> 
> Content-Length: 1588
> 
> 
> At LBL we address the above problem by building base and extensions in
> the same sub-directory and then linking to both base and extensions in
> the appication areas.  That way if there is some weird dependancy to a
> version of either base or extensions then there is no problem.

Just some additional comments about problems with extensions.

When an application is large, i.e. many iocs and many developers, there will
be periods when iocs are on different releases. This is typically the case
when converting to a new release. In general not all developers are prepared
to convert at the same time. Thus we have extensions users that are talking to
collections of iocs that are using a combination of releases.

This is why Jeff has worked so hard to keep the Channel Access protocal
backwards compatible. When the day comes that the CA protocal is changed
so that backwards compatibility is not supported it will mean that entire
applications must change to the new release. For example at APS it will mean
that all iocs and all extensions products will have to be changed at the
same time.

One last comment. Many users and developers are only involved with extension
products. Thus they dont know or care about base other than that their
extension products happen to be build against a particular version of base.

Marty Kraimer

Navigate by Date:: Prev: Re: Solaris 5.x changes to blderrSymTbl Andrew Johnson; Next: Re: TTL --> fibre Bill McDowell; 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: Building for more than one host architecture Marty Kraimer; Next: Building for more than one host architecture Janet B. Anderson; 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