Experimental Physics and Industrial Control System
On Donnerstag, 20. Mai 2010, Michael Davidsaver wrote:
> On 05/19/10 15:26, Benjamin Franksen wrote:
> > On Mittwoch, 19. Mai 2010, Davidsaver, Michael wrote:
> >> The difficultly is cross compiling for RTEMS. I'm not sure if it will
> >> work out in the long term, but I have had positive feedback from the
> >> few people who have used it.
> >
> > It is great mystery to me how you could build an EPICS package at all.
>
> The usual way, lots of trial, and lots of error :)
>
> > What about all the other cross-compiler targets and their specific
> > configuration?
>
> While I've had many frustrations with it, I must say that this is were
> the Base build system helped me. Mostly this just worked.
How?
> Of course I
> only cross-build RTEMS, not other host targets. There is much less
> chance of shared library dependency problems when you don't have shared
> libraries!
I don't understand. This is from base-3.14.11/configure/CONFIG_SITE:
# The cross-compiler architectures to build EPICS for
#
# Currently Supporting:
# linux-386 (linux-x86 host)
# linux-486 (linux-x86 host)
# linux-586 (linux-x86 host)
# linux-686 (linux-x86 host)
# linux-arm
# linux-arm_eb
# linux-arm_el
# linux-athlon (linux-x86 host)
# linux-cris (Axis GNU crosscompiler on linux-x86 host)
# linux-cris_v10 (Axis GNU crosscompiler on linux-x86 host)
# linux-cris_v32 (Axis GNU crosscompiler on linux-x86 host)
# linux-xscale_be
# vxWorks-486
# vxWorks-68040
# vxWorks-68040lc
# vxWorks-68060
# vxWorks-pentium
# vxWorks-ppc603
# vxWorks-ppc603_long
# vxWorks-ppc604
# vxWorks-ppc604_long
# vxWorks-ppc604_altivec
# vxWorks-mpc8540
# RTEMS-at91rm9200ek
# RTEMS-beatnik
# RTEMS-gen68360
# RTEMS-mcp750
# RTEMS-mvme167
# RTEMS-mvme2100
# RTEMS-mvme3100
# RTEMS-mvme5500
# RTEMS-pc386
# RTEMS-psim
# RTEMS-uC5282
#
# Definitions of CROSS_COMPILER_TARGET_ARCHS in
# configure/os/CONFIG_SITE.<host>.Common files will
# override
#
CROSS_COMPILER_TARGET_ARCHS=
How does the debian package know which of them I (a) have installed, and (b)
want to build EPICS against?
One solution I could imagine is to have an epics-base package, and then lots
of dependent packages for each possible cross target, like e.g.
epics-base-vxworks-pentium, etc. Of course these would have to depend on
properly packaged (or at least, installed) target cross compilers.
Cheers
Ben
- References:
- epics debian repository update Davidsaver, Michael
- Re: epics debian repository update Benjamin Franksen
- Re: epics debian repository update Michael Davidsaver
- Navigate by Date:
- Prev:
Re: epics debian repository update J. Lewis Muir
- Next:
asyn R4-13-1 available Mark Rivers
- 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: epics debian repository update Michael Davidsaver
- Next:
Re: epics debian repository update Andrew Johnson
- 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