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: gnumake <arch> does not filter out unwished targets on R3.14.11
From: Andrew Johnson <[email protected]>
To: Jüri Tagger <[email protected]>, "EPICS tech-talk" <[email protected]>
Date: Thu, 24 Sep 2009 09:59:00 -0500
Hi Jüri,

On Thursday 24 September 2009 03:39:27 Jüri Tagger wrote:
>
> I have base-3-14-11 built on Solaris for targets solaris-sparc and
> vxWorks-ppc604_long.

> THE EPICS EXAMPLE CODE WILL COMPILE FOR BOTH, solaris-sparc AND
> vxWorks-ppc604_long, BUT OUR vxWorks specific code will not compile for
> solaris-sparc. (This was not behavior on R3.14.10, the "gnumake
> vxWorks-ppc604_long" did build correctly vxWorks-ppc604_long only.)

This behavior was changed between R3.14.10 and R3.14.11, it was necessary to 
allow the parallel build rules to work properly (make -j option).  As you have 
discovered, you can't rely any more on just running 'make <cross-arch>' if 
your code can't be built on the host architecture, you have to be more 
specific in what you ask the build system to do.

> Any good suggestions how to forbid solaris-sparc build for an application
> more effectively?

Yes, the EPICS build system actually makes this easy to do, you configure the 
Makefile to tell gnumake which targets to build on each operating system; if 
you don't specify a particular OS then the target will be built on all of 
them.  When cross-compiling we always build targets for the host architecture 
first in case there are any programs that must be run to create code for the 
cross-compiled targets.

In your makeBaseApp example application, edit the file VMEApp/src/Makefile.  
To restrict the IOC to be built for vxWorks only, change the line
    PROD_IOC = VME
into
    PROD_IOC_vxWorks = VME

You will need to make a similar change to the name of the LIBRARY_IOC variable 
if you are assembling your vxWorks-only code into a library.

Note that this is the OS class that I'm appended to the variable names, you 
can't use a specific target architecture here, but there are other ways to 
limit builds to specific targets if that's what you need to do (but you might 
be better off just overriding the CROSS_COMPILER_TARGET_ARCH variable in that 
Makefile if that's the case).

Many of the Makefile configuration variables have OS-specific versions like 
this, please look at Chapter 4 of the Application Developer's Guide for 
details.

- Andrew
-- 
The best FOSS code is written to be read by other humans -- Harold Welte



Navigate by Date:
Prev: Re: alarm handler on base 3-14-11 Thomas Birke
Next: Re: alarm handler on base 3-14-11 Matthieu Bec
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: alarm handler on base 3-14-11 John William Sinclair
Next: EPICS Python client application survey Abbott, Michael (DLSLtd,RAL,DIA)
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 ·