Dear all,
In the default config distributions, there are two distinct CONFIG_ARCH
for the mv167 and the mv162.
We have an application using both these targets and realized much code
was probably compiled twice (starting wiht the EPICS core) when there
was no need for it, the diffent flags beeing specifc to the 68040 CPU
rather than the actual boards.
I had to build a whole system, and just realised how much time would be
saved this way. the only issue being some ./bin/mv167 references in my
mv162 startup script (or vice versa)..
My question is: would it make sense (and be safe) to declare a generic
CONFIG_ARCH.68040 ? that would let me clean up the startup script issue.
Regards,
Matthieu
--
Matthieu Bec Gemini Observatory
Tel: +1 808 9742557 670 N. A'ohoku Place
Fax: +1 808 9359235 Hilo, Hawaii 96720, USA
- Replies:
- Re: CONFIG_ARCH mv162/mv167 Marty Kraimer
- Re: CONFIG_ARCH mv162/mv167 Andrew Johnson
- Navigate by Date:
- Prev:
Re: base release 3.13.4 Steven Hartman
- Next:
Re: CONFIG_ARCH mv162/mv167 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
- Navigate by Thread:
- Prev:
Re: interp and mbbi/o-direct Kevin Tsubota
- Next:
Re: CONFIG_ARCH mv162/mv167 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
|