Company Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI

LEP_x_ScriptLinker.vi (Microprocessor SDK)

LabVIEW 8.6 Microprocessor SDK Help
June 2008

NI Part Number:
372197B-01

»View Product Info

LEP_x_ScriptLinker.vi, where x is a subtarget and/or an OS, links all intermediate object files, external libraries, run-time libraries, and operating system libraries into an embedded application. LEP_x_ScriptLinker.vi is located in the following directory:

labview\Targets\company_name\Embedded\os\os_LEP_TargetPlugin

where os is the target operating system.

You must implement LEP_x_ScriptLinker.vi if you require behavior that differs from the default implementation. Use the base example target default implementation for your OS of LEP_x_ScriptLinker.vi and override only the necessary features. To override the default implementation, wire an LEP_x_ScriptLinker.vi VI reference to the Linker Script input of LEP_x_Build.vi. Your custom implementation of LEP_x_ScriptLinker.vi must have the same connector pane as the default implementation.

Note  Some example targets avoid long command lines by using prjObjs.lst to obtain a list of all modules. LEP_x_Build.vi generates prjObjs.lst and lists all binary modules and libraries.

LEP_x_ScriptLinker.vi can execute the C linker directly by calling the System Exec VI. You also can use a batch file to directly execute the linker. Use a batch file if you need to set linker-specific system variables before the linker can execute. For example, the VxWorks example targets use a batch file because you must set the Tornado system variables before the C compiler executes.


Resources


 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit