Subject: |
Re: [Merge] ~dirk.zimoch/epics-base:dynamicVxWorksVmeFunctionBinding into epics-base:7.0 |
From: |
Dirk Zimoch via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Wed, 15 May 2019 07:26:58 -0000 |
The problem here was that not every vxWorks system has a VME bus and thus loading EPICS base failed with unresolved symbols. This applies to each library/module that has vxWorks support for VME mixed with code for other useful stuff. At the moment if you want the other stuff you must have VME. So yes, that may apply to devLib2 as well.
However so far I only had one such system, that is an old CompactRIO fom NI. And on that system I do not use devLib2. So I have not noticed a problem.
--
https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/367253
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.
- References:
- [Merge] ~dirk.zimoch/epics-base:dynamicVxWorksVmeFunctionBinding into epics-base:7.0 Dirk Zimoch via Core-talk
- Navigate by Date:
- Prev:
Re: [Merge] ~dirk.zimoch/epics-base:dynamicVxWorksVmeFunctionBinding into epics-base:7.0 mdavidsaver via Core-talk
- Next:
_WIN32_WINNT defines in EPICS base Freddie Akeroyd - UKRI STFC via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: [Merge] ~dirk.zimoch/epics-base:dynamicVxWorksVmeFunctionBinding into epics-base:7.0 mdavidsaver via Core-talk
- Next:
[Merge] ~dirk.zimoch/epics-base:dynamicVxWorksVmeFunctionBinding into epics-base:7.0 noreply--- via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|