Content deleted Content added
m It was a minor edit chaged the phrase "third=party standards" to "third party standards" |
No edit summary |
||
Line 50:
Building a stand-alone application with LabVIEW requires the Application Builder component which is included with the Professional Development System but requires a separate purchase if using the Base Package or Full Development System.<ref name="Building a Stand-Alone Application">{{cite news |url= http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/building_a_stand_alone_app/ | publisher=National Instruments |title= Building a Stand-Alone Application }}</ref> Compiled [[executable]]s produced by the Application Builder are not truly standalone in that they also require that the LabVIEW run-time engine be installed on any target computer on which users run the application.<ref name="Using the LabVIEW Run-Time Engine">{{cite news |url= http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/using_the_lv_run_time_eng/ | publisher=National Instruments |title= Using the LabVIEW Run-Time Engine }}</ref> The use of standard controls requires a [[runtime library]] for any language and all major operating system suppliers supply the required libraries for common languages such as C. However, the runtime required for LabVIEW is not supplied with any operating system and is required to be specifically installed by the administrator or user. This requirement can cause problems if an application is distributed to a user who may be prepared to run the application but does not have the inclination or permission to install additional files on the host system prior to running the executable.
According to the [[National Instruments]] [[license agreement]] an executable
<pre>(1.) You include the following copyright notice "Copyright © [insert year] National Instruments Corporation.
|