Dirk, Rod,
> Normally I don't build on the local machine. But it depends. If it is
> large enough to have the compiler installed and you build locally, then
> your EPICS_HOST_ARCH is linux-arm* and it is not treated as a cross
> build. And you will automatically have caget etc.
That's the 1st thing I tried.
It could potentially work, but you still have to create your configuration files.
iBut when building, it is ... slow. So in a debugging phase, good luck!
> In src/catools/Makefile you find:
> LIBRARY_HOST += catools
> PROD_HOST += caget camonitor cainfo caput
> This builds caget etc only for the host, not for the cross targets.
> To build the tools for all cross Linux IOCs, you may try to add:
> LIBRARY_IOC_Linux += catools
> PROD_IOC_Linux += caget camonitor cainfo caput
I didn't try the above. But I found I simply needed
VALID_BUILDS += Host
in my CONFIG_SITE.Common.linux-arm4vtl
In linux-arm, we already have
VALID_BUILDS = Ioc (which basically means build the libs)
Check configure/RULES_BUILD for more info
Thank you,
--
Emmanuel
- Replies:
- Re: EPICS on ARM (continued) Andrew Johnson
- 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
- Re: EPICS on ARM (continued) emmanuel_mayssat
- Re: EPICS on ARM (continued) Dirk Zimoch
- Navigate by Date:
- Prev:
RE: EPICS CA problems Jeff Hill
- Next:
Re: EPICS on ARM (continued) 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
- Navigate by Thread:
- Prev:
Re: EPICS on ARM (continued) Dirk Zimoch
- Next:
Re: EPICS on ARM (continued) 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
|