2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 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: Strange UDP message on VxWorks 6.9 |
From: | "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov> |
To: | Michael Davidsaver <mdavidsaver at gmail.com> |
Cc: | EPICS core-talk <core-talk at aps.anl.gov> |
Date: | Mon, 22 Nov 2021 19:04:50 +0000 |
On Nov 19, 2021, at 2:26 PM, Michael Davidsaver via Core-talk <core-talk at aps.anl.gov> wrote:
Currently the configure/os/CONFIG.Common.vxWorksCommon definitions don’t support building .munch files for TESTPROD (or TESTPROD_vxWorks) targets, only for PROD (and hence PROD_vxWorks) targets.
The VxWorks test harnesses aren't actually intended to be installed — the .dbd files aren’t the only files that the test code needs to access. Because of the above limitation though we have to build them as PROD targets, and the files get installed because
of that. Test programs are intended to be run after doing a cd to the appropriate O.<arch> directory which is where ‘make runtests’ and friends run them from for all of the host architectures. In my scripts for running the tests on VxWorks I cd to the test
build directories, load the .munch files and run the harness programs directly and they work fine for me.
I don’t have time to work on fixing the TESTPROD builds myself and I’m not sure that it’s really worth the effort, although I wouldn’t object to it being done.
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|