Experimental Physics and Industrial Control System
On Tue, 2005-11-22 at 17:58 -0800, Mark Wagner wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, Oct 27, 2005 at 11:16:45AM -1000, Maren Purves wrote:
>
> > looks like you have a Makefile.Vx in your soruce directory.
> > If so, either delete it or rename it to something else.
>
> There was no Makefile.Vx in my source directory.
>
> I followed the maze of Makefile includes to the culprit. In
>
> ${MY_EPICS_BASE}/configure/CONFIG_COMMON
The extensions tree also has a configure directory.
Most of the extensions that we use if not all are host-side only.
For example, CA client apps, EPICS database tools, or some other misc
EPICS utility are host-based.
So, what we have always done when building with R3.14.7; set
the variable "CROSS_COMPILER_TARGET_ARCHS" to NULL
Modify:
$(EPICS_EXTENSIONS)/configure/CONFIG
The following is what we have:
================ CONFIG ============================
[williams@ics-accl-srv1 configure]$ more CONFIG
# $Id: CONFIG,v 1.1 2004/06/02 06:04:06 williams Exp $
include $(TOP)/configure/CONFIG_EXTENSIONS
# Add any changes to make rules here
CROSS_COMPILER_TARGET_ARCHS =
====================================================
The above works great and I hope it is the recommended way.
If you don't want all extensions to inherit the
CROSS_COMPILER_TARGET_ARCHS setting then you can override things in the
local Makefiles of desired extension package. For example, SDDS may
some target-side tools as well as host-side?
HTH,
Ernest L. Williams Jr.
SNS Control Systems Group
ORNL
>
> there is
>
> BUILD_ARCHS = $(EPICS_HOST_ARCH) $(CROSS1) $(CROSS2)
>
> Changing that to
>
> BUILD_ARCHS = $(EPICS_HOST_ARCH)
>
> fixed the problem. (I then changed it back after compiling edm.)
>
> I'm an EPICS newbie so I'm looking for a bit of enlightenment with these
> questions:
>
> Why would edm, or any other extension, use BUILD_ARCHS, when they will
> run on the EPICS_HOST_ARCH only?
>
> How can I tell edm, without touching stuff in ${MY_EPICS_BASE}, that it
> shouldn't build for the target(s), only the host? I tried mucking with
> stuff in ${EPICS_EXTENSIONS}/configure and ${EPICS_EXTENSIONS}/src/edm
> to no avail.
>
> Is there an extension that is a shining example of the proper use of
> the EPICS 3.14 build system?
>
> > Mark Wagner wrote:
>
> > >I'm trying to build EDM on a linux-x86 host, which seems to go OK.
> > >However, it seems as though it is trying to be built for the vxWorks-68040
> > >target too, which causes all sorts of problems. How can I make it not
> > >do that?
> > >
> > >epics 3.14.7
> > >edm 1-10-1zf
>
> > >extensionsConfigure_20040406
> > >extensionsConfig_20040406
>
> - --
> Mark Wagner [email protected] 206-598-0302
> Unix System Administrator, Radiation Oncology
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFDg8y0vOs2g/c480IRAlJDAJ9fcylurjZuLp9ofGeDsGO4BL/wtQCdE5CX
> ueo46SB9CVWzWItMF2fjsU0=
> =g2ZX
> -----END PGP SIGNATURE-----
- References:
- EDM wants to build on vxWorks-68040 target. Why? Mark Wagner
- Re: EDM wants to build on vxWorks-68040 target. Why? Mark Wagner
- Navigate by Date:
- Prev:
RE: EPICS base compiling using Visual C++ 2005 Express guobao shen
- Next:
RE: EPICS base compiling using Visual C++ 2005 Express Jeff Hill
- 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: EDM wants to build on vxWorks-68040 target. Why? Mark Wagner
- Next:
RE: EDM wants to build on vxWorks-68040 target. Why? Singleton, SJ (Steve)
- 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