Rod, Dirk,
I was able to compile and build the libs for my arm platform.
To my surprise the catools (caget, etc) are not built (only the libs are)
I don't need them for my iocs, but would be nice to have them for troubleshooting.
(my arm linux is the etch debian version, i.e. in theory I could ssh to it and caget from
it). What is the directive to build the <top>/bin/linux-arm_el ?
Obviously the files are built on my linux x86_64 machine.
But how does the arm access those files, i.e what is common practice?
1/ Do you nfs mount the partition on the arm and access the lib from there?
2/ Do you copy the files on the arm? scp, ftp, unison, etc...
3/ Do you nfs mount the arm and build on local machine?
I would prefer my embedded system to be standalone. So 2 and 3 seem to make sense.
But what do you/others do?
Thanks,
--
Emmanuel
- Replies:
- Re: EPICS on ARM (continued) Dirk Zimoch
- References:
- RE: Thread model for EPICS on ARM CPU michael.abbott
- Re: Thread model for EPICS on ARM CPU Rod Nussbaumer
- EPICS on ARM (continued) emmanuel_mayssat
- Re: EPICS on ARM (continued) Dirk Zimoch
- Navigate by Date:
- Prev:
Some Channel Access Questions Ben Franksen
- Next:
RE: ChannelArchiver build problem with 3.14.11 on Suse linux Shankar, Murali
- 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 on ARM (continued) Dirk Zimoch
- Next:
Re: EPICS on ARM (continued) Dirk Zimoch
- 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
|