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: areaDetector build system question |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Jörn Dreyer <j.dreyer at hzdr.de>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Thu, 13 Mar 2025 16:42:54 +0000 |
Hi Jörn, At APS we use Sumo to build AreaDetector (including ADCore and ADSupport), many of the standard plugins as external modules, and many IOCs which use these. I suggested changes to the AreaDetector build system
to make that work, although
my PR has bit-rotted somewhat in the 3-4 years since I last worked on it. Our local AreaDetector version has some additional changes that aren’t in the PR, but the plugins don’t require any modification IIRC. Here is the configure/MODULES file from our camera IOC area, showing that it is possible to do this: $ cat configure/MODULES { "extra": [ "ADCORE=$(AREA_DETECTOR)/ADCore", "ADSUPPORT=$(AREA_DETECTOR)/ADSupport" ], "module": [ "ADARAVIS:2.2.1-C2-1", "ADGENICAM:1.10-C2-1", "ADPOINTGREY:2.9-C2-1", "ADSPINNAKER:3.3-C2-1", "AREA_DETECTOR:3.12.1-C2-2", "ASYN:4.42-C2-2", "AUTOSAVE:5.10.2-C2-1", "BASE:7.0.6.1-C2-3", "BUSY:1.7.3-C2-1", "CALC:3.7.4-C2-1", "IOCSTATS:3.2.0-C2-2", "IOCSTD:4.5.0-C2-1", "NDDRIVERSTDARRAYS:1.4-C2-1", "SEQ:2.2.9-C2-1", "SSCAN:2.11.5-C2-1", "ZLIB:1.2.11-C2-1" ] } - Andrew -- Complexity comes for free, Simplicity you have to work for. |