LEP_x_ScriptLinker.vi Implementation Example (Microprocessor SDK)
The VxWorks CMD565 example target implements a subtarget-specific LEP_vxworks_cmd565_ScriptLinker.vi, which is located in the following file:
 | labview\Targets\NI\Embedded\vxworks\cmd565\vxworks_cmd565_LEP_TargetPlugin\LEP_vxworks_cmd565_Build.vi |
This custom implementation overrides the default implementation of the LEP_vxworks_ScriptCompiler.vi, LEP_vxworks_ScriptLinker.vi, and LEP_vxworks_Config.ctl. Notice the Case structure with target-specific VIs in this custom implementation. The VIs in the Case structure never execute but are always loaded into memory. Because the VIs are loaded into memory, you can use the Open VI Reference function to refer to VIs by name instead of absolute path.
VxWorks module targets do not link with the operating system libraries because the VxWorks module loader resolves all symbols. The VxWorks and eCos example targets do not have pre-compiled run-time libraries, so LEP_vxworks_cmd565_ScriptLinker.vi also must link with the run-time library intermediate files.