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: Building an Epics module only for a target (not host) |
From: | "Florian Feldbauer" <[email protected]> |
To: | "Michael Davidsaver" <[email protected]> |
Cc: | [email protected] |
Date: | 28 Feb 2013 15:54:09 +0100 |
Ok, thanks for the info! On 02/28/2013 03:49 PM, Michael Davidsaver wrote:
On 02/28/2013 08:33 AM, Florian Feldbauer wrote:Hey all, is there a way to build an EPICS module (like e.g. asyn) only for a certain target, which is _not_ the host? Currently I build the module for my host architecture and the target architecture, but I need it only for the target... Best regards, FlorianIn addition to the 'PROD' variable you can also use 'PROD_$(OS_CLASS)' and 'PROD_$(ARCH)'). For example:PROD_RTEMS = rtemsSpecificIoc PROD_linux-x86 = reallySpecificIocBeware of the second form, it is very specific. This example will not build for the debug target 'linux-x86-debug'.This also works for 'LIBRARY'. For some examples see 'configure/Sample.Makefile' from Base.http://bazaar.launchpad.net/~epics-core/epics-base/3.15/view/head:/configure/Sample.Makefile#L181
-- ---------------------------------------- | Dr. rer. nat. Florian Feldbauer | | | | Helmholtz-Institut Mainz / | | Johannes Gutenberg-Universität Mainz | | Johann-Joachim-Becher-Weg 45 | | D-55128 Mainz | | | | Office: 01/217 | | Phone: (+49)6131 / 39-25829 | ----------------------------------------