EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Cross Building Extensions
From: Ralph Lange <[email protected]>
To: David Dudley <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Fri, 04 Dec 2009 16:33:52 -0500
Just for completeness and to confuse you....

The change Janet suggests will build HOST prods and libraries for linux-xscale_be for all applications, everywhere. (To avoid conflicts with version upgrades, it should rather be done in a copy of that file, called .../configure/CONFIG_SITE.Common.linux-xscale_be.)

If you want this behavior only for one application, you could remove the _HOST qualifier from the LIBRARY_HOST and PROD_HOST definitions in that application's Makefiles, which will build only this application for HOST and all IOC type architectures.

If you want only this application to build on the HOST and only one of your IOC target architectures, you could leave the *_HOST definitions in and add a similar *_IOC_linux-xscale_be definition to each one.

Ralph


Janet Anderson wrote:
R3.14.11 base contain a configure/CONFIG.Common.linux-xscale_be file. It is set up to build only IOC prods and libraries. Comment out the line "VALID_BUILDS = Ioc" to build both HOST and IOC prods and libraries.

David Dudley wrote:
I have a project where I need to cross build some of the EPICS extensions for another architecture.

Specifically, I want to build the ChannelArchiver to run on a remote Linux host.

I already have the IOS compiled for the host (linux-xscale_be), and it works well, with all the libraries and programs functional on that architecture, but to make the machine I’m setting up an independent system, I need to run the ChannelArchiver as well on that device.

I defined ‘CROSS_COMPILER_TARGET_ARCHS’ in the extensions configure directory to ‘linux-xscale_be’, and when I build, I create a xscale_be bin directory, however the build system doesn’t pick up the target build tools, so it’s building 2 copies of the host programs.

What do I adjust to make the extensions build system pick up the proper toolset?

David Dudley

References:
Cross Building Extensions David Dudley
Re: Cross Building Extensions Janet Anderson

Navigate by Date:
Prev: Re: Cross Building Extensions Janet Anderson
Next: camonitor and caget - displaying unsigned longs in hexadecimal Allison, Stephanie
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Cross Building Extensions Janet Anderson
Next: camonitor and caget - displaying unsigned longs in hexadecimal Allison, Stephanie
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·