Preparing Files to Create a Build Output

Before you can create a build specification, prepare your files for distribution.

For example, if you plan to distribute a stand-alone application to a system that does not have the LabVIEW Development System installed, be sure any properties and methods you use are supported in the LabVIEW Runtime.

To prepare LabVIEW source files to create a build output, complete the following steps.

  1. Open the LabVIEW project from which you want to build the output.
    Note You must build an output from a project, not from an individual VI.
  2. Save the entire project to ensure that all VIs are saved in the current version of LabVIEW.
  3. Verify the settings in the VI Properties dialog box for each VI.
    If you plan to distribute your build output, ensure that the settings in the VI Properties dialog box are accurate for the built version of your VIs.
    Note If your build output contains VIs with separate compiled code, configure settings for those VIs on the Source Files Settings page of the Properties dialog box for your application.
    For example, to polish the appearance of your build output, verify the settings on the following pages of the VI Properties dialog box:
  4. Verify that the paths used in the development environment still behave correctly on destination computers.
    • If the project loads VIs dynamically, use relative paths, instead of absolute paths, to specify the location of the VI.

      Because file hierarchies can vary on different computers, relative paths ensure that paths function correctly in both the development environment and the destination computers on which the application runs.

      Note If your application uses the 8.x file layout, you may need to use a different relative path on the destination computer from the relative path in the development environment.
    • You can specify the destination for the generated files on the Destinations page of the properties dialog box for the build specification you are creating.
  5. Verify that the Current VI's Path function returns the path you expect.

    In a stand-alone application or shared library, the Current VI's Path function returns the path to the VI in the application file and treats the application file as an LLB.

    For example, if you build foo.vi into an application, the function returns a path of C:\..\Application.exe\foo.vi, where C:\..\Application.exe represents the path to the application and its filename.

  6. Ensure that VI Server properties and methods work as expected in the LabVIEW Runtime.
    Notice The LabVIEW Runtime does not support some VI Server properties and methods. Avoid using these properties and methods in the VIs that you include in an application or a shared library.

    You can run the Built Application Compatibility test from the VI Analyzer Toolkit to ensure that your VI Server properties are compatible with the LabVIEW Runtime.