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: anyone ever crosscompile pvaPy? |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Peter.Milne at d-tacq.com" <Peter.Milne at d-tacq.com> |
Cc: | "Veseli, Sinisa" <sveseli at anl.gov>, EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Fri, 22 May 2020 15:27:00 +0000 |
Hi Peter,
On May 22, 2020, at 3:23 AM, Peter Milne via Tech-talk <tech-talk at aps.anl.gov> wrote:
The important entry in src/pvaccess/Makefile is the line
LOADABLE_LIBRARY_HOST += pvaccess Since pvaPy is a dynamic library that gets loaded by Python, there are no binaries to create so no use of the PROD or PROD_HOST variables in the Makefile. Change the above to LOADABLE_LIBRARY and it should start cross-compiling for your target.
Hopefully you and Sinisa can work out some way to adjust the build so cross-builds like this can be configured more easily, but I suspect it may always need some kind of manual configuration to enable it.
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|