| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: no envPaths in application of base 3.14.11 |
| From: | Ralph Lange <[email protected]> |
| To: | [email protected] |
| Date: | Wed, 16 Feb 2011 10:32:42 +0100 |
On 16.02.2011 02:35 Mi Qingru wrote:
Hi, CROSS_COMPILE_TARGET_ARCHS in base 3.14.11 may be wrong. I set it to "linux-x86". As I set it to "linux-386", envPaths is generated in myapps/iocBoot/iocmyapps by make. Whatever CROSS_COMPILE_TARGET_ARCHS is set to in base 3.14.8.2, envPaths will be generated. I think the difference is in the file RULES.ioc .
Things I noticed: The name of that variable is CROSS_COMPILER_TARGET_ARCHS (with an R at the end of the second part).If you look at the list of supported cross-compiler architectures (e.g in BASE/configure/CONFIG_SITE), you will find that "linux-x86" is *not* a supported cross-compiler architecture.
Nevertheless, "linux-x86" *is* a supported host architecture. Compiling the example app with an empty CROSS_COMPILER_TARGET_ARCHS and selecting "linux-x86" as the IOC architecture does create the envPaths file correctly.
~Ralph