Experimental Physics and
| |||||||||||||||||||||||||||
|
Finally, I'm able to build my own vxTestHarness.munch. I put it onto my vxWorks system, load it, and run the command epicsThreadPrivateTest, all 5 tests passed. Now I have no idea what has caused our problem :( Actually we DO use EPICS build system, to build the static libraries (.a files on vxWorks). And then we link all the static libraries that we need into a single dynamic library (.o file on vxWorks). I'm not sure if there's munching stuff happening during the linking process. Could that be the issue? Thanks, Lorna Zhang
Hi Lorna, On 2011-06-30 [email protected] wrote: > We are not using the EPICS build system. Do you use C++ in any of the other code you are running on vxWorks? If EPICS is the only source of C++ code in your system then your build system may not be properly handling the initialization code for C++ static constructors and destructors, which is what the munch process is for. This is documented by Wind River in their VxWorks Kernel Programmers Guide; for vxWorks 6.3 see section 11.5 "Downloadable Kernel C++ Modules". > Is it feasible that I copy your built vxTestHarness.munch to my vxWorks > system, load it, and then run the test commands you've mentioned? I don't have access to vxWorks 6.3, and I don't think any binary I build using either vxWorks 5.5.2 or 6.8 would work properly on your version. You will have to build EPICS Base yourself using our build system. You can find instructions on the tools you need to do that on Windows at http://www.aps.anl.gov/epics/base/win32.php - Andrew -- Optimization is the process of taking something that works and replacing it with something that almost works, but costs less. -- Roger Needham
| ||||||||||||||||||||||||||
ANJ, 18 Nov 2013 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |