Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: EPICS build on armv6l
From: Andrew Johnson <anj@aps.anl.gov>
To: tech-talk@aps.anl.gov
Cc: Florian Feldbauer <florian@ep1.ruhr-uni-bochum.de>
Date: Tue, 12 Jun 2012 10:30:43 -0500
Hi Florian,

On 2012-06-12 Florian Feldbauer wrote:
> Currently arm is only supported as target not as host for build.
> Since the Raspberry Pi has a gnu c compiler and all
> the libraries I need (also a x-server), would it be possible to build
> EPICS directly on this system instead of building it on a different system?

Yes, although as Jeff said you might need to add a few things to the 
configure/os directory to get it to build.  Since you're self-hosting I think 
you should be able to use the generic target name linux-arm for this build, 
which should simplify the Base configuration process.

You will need to create the file CONFIG.linux-arm.Common containing the line
    include $(CONFIG)/os/CONFIG.UnixCommon.Common
but that might be all you actually have to do.  CONFIG.Common.linux-arm may 
look like it's only set up for cross-compilation, but those settings are 
actually overrides to variables set in CONFIG.Common.UnixCommon so first try 
building without making any changes there.

In case it's not clear, files names *.<host>.Common are included whenever 
building on <host> irrespective of the target; files named *.Common.<target> 
are included whenever compiling for <target> on any host; files named 
*.<host>.<target> are used whenever that particular combination of <host> and 
<target> are involved.  Files named CONFIG.*.* contain default settings for 
the build process, while files named CONFIG_SITE.*.* are intended for site-
specific settings such as paths that might vary (location of cross-compilers 
etc.).

After a top-level 'make' succeeds, you will want to use 'make runtests' to 
execute the build-in test programs (note that epicsMessageQueueTest takes 5 
minutes to run, don't assume it has crashed when the messages stop mid-test).

Hope this gets you started, ask if you get stuck.  I would be interested in 
adding your configuration files to the Base distribution if you would like to 
contribute them once you have everything working.

- Andrew
-- 
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte

Replies:
RE: EPICS build on armv6l Tim Robinson
References:
EPICS build on armv6l Florian Feldbauer

Navigate by Date:
Prev: RE: EPICS build on armv6l Hill, Jeff
Next: thermocouple solutions Wesley Moore
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: RE: EPICS build on armv6l Hill, Jeff
Next: RE: EPICS build on armv6l Tim Robinson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·