When an RTP containing dynamic dependencies is spawned, the dynamic linker reads a delimited sequence of directory paths. The dynamic linker evaluates paths in a specific precedence order:
: If your application uses third-party libraries (like RTI Connext DDS ), those paths must be added to LD_LIBRARY_PATH alongside the path to the VxWorks libc.so . Summary Review Table Description Standard Variable LD_LIBRARY_PATH Application Type User-space Real-Time Processes (RTP) Common Path Often points to /romfs/lib or external storage like /sd0 Separators Semicolon ( ; ) or comma ( , ) in many VxWorks versions LD_LIBRARY_PATH – or: How to get yourself into trouble!
:
VxWorks provides separate host-side development tools and target-side runtime environments to manage variables. 1. Setting Variables via the Target Shell
Vxworks Ld_path Environment Variable ((free))
When an RTP containing dynamic dependencies is spawned, the dynamic linker reads a delimited sequence of directory paths. The dynamic linker evaluates paths in a specific precedence order:
: If your application uses third-party libraries (like RTI Connext DDS ), those paths must be added to LD_LIBRARY_PATH alongside the path to the VxWorks libc.so . Summary Review Table Description Standard Variable LD_LIBRARY_PATH Application Type User-space Real-Time Processes (RTP) Common Path Often points to /romfs/lib or external storage like /sd0 Separators Semicolon ( ; ) or comma ( , ) in many VxWorks versions LD_LIBRARY_PATH – or: How to get yourself into trouble!
:
VxWorks provides separate host-side development tools and target-side runtime environments to manage variables. 1. Setting Variables via the Target Shell