Matthieu Bec wrote:
>
> 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.
To add to Marty's answer and for the benefit of other readers, from EPICS
3.14 we have changed the target naming scheme to
<os>-<cpu>[-<toolset>]
where
<os> = vxWorks, RTEMS, solaris, linux or win32
<cpu> = 68040, 68040lc, ppc604, x86 etc.
<toolset> is only used when there are multiple compilers available for the
os/cpu combination (eg borland rather than the default microsoft compiler
on WIN32, gnu rather than SunPro on Solaris [this is not in Alpha1]). This
can make the build directory names rather long (O.solaris-sparc-gnu,
O.win32-x86-borland), but means we can build all the targets and toolset
combinations in a single installation.
On RTEMS the <cpu> portion is the BSP name, I haven't worked out whether
we can switch to just using the CPU type yet.
- Andrew
--
Every great idea appears crazy to start with.
- References:
- CONFIG_ARCH mv162/mv167 Matthieu Bec
- Navigate by Date:
- Prev:
Re: CONFIG_ARCH mv162/mv167 Marty Kraimer
- Next:
Re: base release 3.13.4 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: CONFIG_ARCH mv162/mv167 Marty Kraimer
- Next:
R3.14.0alpha1 Leonard J. Reder
- 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
|