Hi,
On Tuesday 04 January 2011 05:19:46 王林 wrote:
> I have been confused about where the vxworks os library files are for a
> long time, since the document EPICS-3.14 README said that you must have
> Tornado 2 installed if any of your target systems are vxWorks systems.
> Tornado 2 provides the cross-compiler and header files needed to build for
> these target systems, which means that we don't need library files for
> vxworks program development, and it seems very diffenent from Linux and
> Windows. After reading some documents, now can I understand it as this?
You are correct that the way we have traditionally done EPICS development for
vxWorks is different than for the workstation operating systems such as Linux
and Windows.
> The vxworks os libraries have already been compiled into the vxworks kernel
> image, the module will find the os libraries by the vxworks symbol table
> after loaded to target instead of linking on the host before loaded. Am I
> right? Some comment?
Correct, the IOC image that we build for vxWorks targets contains only the
EPICS code, and relies on the OS libraries having already been loaded as part
of the vxWorks boot image.
It should be possible to build an IOC image as a stand-alone bootable vxWorks
binary, but the EPICS build system does not contain the rules necessary to do
that and I'm not aware of anyone having actually done it. This would require
linking with the vxWorks OS library files and thus would be more conventional
(we do build binaries for RTEMS like this). If anyone manages to do this I
would be interested in adding the additional rules to future releases of EPICS
Base.
- Andrew
--
If a man is offered a fact which goes against his instincts, he will
scrutinize it closely, and unless the evidence is overwhelming, he will
refuse to believe it. If, on the other hand, he is offered something
which affords a reason for acting in accordance to his instincts, he
will accept it even on the slightest evidence. -- Bertrand Russell
- References:
- where are the vxworks os library files 王林
- Navigate by Date:
- Prev:
Writing mbbo/mbbi text labels using asynPortDriver/areaDetector tom.cobb
- Next:
record STAT = SCAN John Dobbins
- 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
- Navigate by Thread:
- Prev:
where are the vxworks os library files 王林
- Next:
Writing mbbo/mbbi text labels using asynPortDriver/areaDetector tom.cobb
- 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
|