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: wanted: rule to build products with own CFLAGS inside single Makefile |
From: | Andrew Johnson <[email protected]> |
To: | Dayle Kotturi <[email protected]> |
Cc: | [email protected] |
Date: | Wed, 30 May 2007 15:31:23 -0500 |
I have an RF phase and amplitude detection application which needs to be built slightly differently for each RF station. I want to keep the code as one single app and build multiple products. I need each product to have its own CFLAGS definition to pick up its correct code.
# 5/30/7: option 1. this doesn't work. None of these flags get used because # <product>_CFLAGS_* is not interpreted pad-gen_CFLAGS_RTEMS += -DPAD_GEN pad-ref_CFLAGS_RTEMS += -DPAD_REF pad-lsr_CFLAGS_RTEMS += -DPAD_LSR pad-l1xkly_CFLAGS_RTEMS += -DPAD_L1XKLY pad-kly_CFLAGS_RTEMS += -DPAD_KLY pad-bph_CFLAGS_RTEMS += -DPAD_BPH
- Andrew -- The right to be heard does not automatically include the right to be taken seriously. -- Hubert H. Humphrey