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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: First Use Of 3.14.12.2 - target builds try to produce code for host also |
From: | Ralph Lange <[email protected]> |
To: | EPICS Tech Talk <[email protected]> |
Date: | Fri, 05 Oct 2012 23:14:51 +0200 |
On Fri Oct 05 2012 22:49:54 GMT+0200
(CEST), Duane Voy <[email protected]> wrote:
I have built 3.14.12.2 on linux-x86 host for cross development to vxWorks-ppc604_long targets. When I do 'gmake vxWorks-ppc604_long' the make system tries to produce code for linux-x86 as well, which is doomed to failure with code referencing VxWorks headers. This behavior is different from any that I have seen in versions <= 3.14.10. I have been reading documentation and googling and greping, and have tried everything I can think of to make CROSS_COMPILER_TARGET_ARCHS be -just- vxWorks-ppc604_long. All with no luck. Hi Duane, this behavior change has been documented in the release notes [1], see "Build system dependency change" in the section for 3.14.11. The key is to change the Makefiles for vxWorks-only modules to build vxWorks-only stuff only for vxWorks. (Not as trivial as it sounds.) In most cases this involves moving definitions e.g. from LIBRARY to LIBRARY_vxWorks, from PROD to PROD_vxWorks etc. - see the chapter "Build Facility" (paragraph "Makefile definitions") in the App Developers Guide. HTH, ~Ralph [1] http://www.aps.anl.gov/epics/base/R3-14/12-docs/RELEASE_NOTES.html |