> What are the major problems with moving to 5.3? Will apps compiled with
> 5.2 headers not run?
Suprisingly many bits and pieces *WILL* run, but it's not
worth trying.
> We're on the edge of making this transition, and
> if we absolutely gotta convert everything in one swell foop, it probably
> aint' gonna happen real soon. And the longer we put it off, the worse
> the pain is gonna be!
If you look back though the tech-talk archives, many of us have
given simple prescriptions for this transition. For building
EPICS itself, just a few lines have to be changed in
startup/Site.cshrc and config/CONFIG_SITE and one or two more.
If you are using any of the application-building techniques
that rely on the built-in rules (no hand-coded cc lines)
then you should have no problems.
And the latest R3.13beta12 is certainly "5.3 ready".
> I guess the good news is that it looks to me like the structure of 3.13.0
> makes it easier, altho perhaps a little spendy in terms of disk space,
> to move forward one system (ioc) at a time.
This is really a function of how you build and boot your applications.
Many sites (CEBAF, LBL, those who use UAE, etc) can independently
boot any IOC from any VxWorks and couple that with any version
of EPICS.
- Navigate by Date:
- Prev:
Re: mv177 Bill Brown
- Next:
Perl on HPUX Ralph Lange
- 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: mv177 Bill Brown
- Next:
Perl on HPUX Ralph Lange
- 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
|