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: How to build MEDM (Jetson nano) |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Hinko Kocevar <Hinko.Kocevar at ess.eu> |
Cc: | 신동호 <dhshin at etri.re.kr>, EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Tue, 22 Sep 2020 16:37:24 +0000 |
Hi Hinko,
On Sep 22, 2020, at 9:32 AM, Hinko Kocevar <Hinko.Kocevar at ess.eu> wrote:
By ‘native’ I mean this is a build on the linux-aarch64 processor itself which is running Ubuntu, it’s not a cross-compile at all. I only just added the native CONFIG files for linux-aarch64 to the Base-7.0 branch when Dong Ho asked about this a week or
two ago.
If you configured extensions to be cross-compiled on the same Ubuntu release maybe all the X11 and Motif header files would be the same for the cross-target if you could install them, but the build-time library paths would be different so you wouldn’t
be able to test the native CONFIG_SITE files yourself. I’m not too sure whether this is worth doing.
I asked my boss if I can buy an aarch64 box (an R.Pi-4) to test out this kind of thing, but he hasn’t said yes yet (and I suspect there are a few other R.Pi enthusiasts here who might be quicker at setting this up than I would given everything else I’m
supposed to be working on).
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|