You are here: NI Home > Support > Product Reference > Manuals > LabVIEW 8.5 Help

Use this page of the Shared Library Properties dialog box to change advanced settings for a shared library.

This page includes the following components:

• Enable debugging—Enables debugging for the application or shared library.
  • Wait for debugger on launch—Sets the application or shared library to load but not run until the user enables it to run through the LabVIEW debugging controls. Place a checkmark in the Enable debugging checkbox to activate this option.
• Copy error code files—Adds copies of XML-based LabVIEW error code text files from the project\errors and user.lib\errors folders to the run-time engine.

  Note  You must manually create an errors folder in the labview\user.lib directory to organize your error code files.

• Use the default project aliases file—Copies the project aliases file with the application or shared library. If you remove the checkmark from the checkbox, the Select Project File dialog box appears and you can select another aliases file in the project.
  • Aliases file in project—Specifies the aliases file to use with the application or shared library if you do not enable Use the default project aliases file. Click the Browse Project button to display the Select Project File dialog box, which you can use to select an aliases file.
• Delay operating system messages in shared library—Delays operating system messages until calls to shared library functions end or until you load a modal window from the shared library. A modal window is a type of window that remains active or remains on top of all other LabVIEW windows until you close the window or open another modal window. You cannot interact with other windows while a modal window is open. Most dialog boxes in LabVIEW are modal windows. The delay allows shared library functions to run without interruption and prevents you from calling the same shared library file while a shared library function runs. Remove the checkmark from this checkbox if you want to process operating system messages while shared library functions run.
• Include additional LabVIEW header files—Copies into the built shared library any additional LabVIEW header files that are referenced by the header file that is generated during the build process. Including additional header files allows you to use a LabVIEW built shared library in C or another language that requires those header files.
• Enable Enhanced DSC Run-Time support—This option only appears if you have the LabVIEW Datalogging and Supervisory Control (DSC) Module installed. Builds the application with the enhanced LabVIEW (DSC) Module Run-Time Engine. The DSC Module Run-Time Engine adds additional support for programmatic project library and shared variable management in applications that you build with the DSC Module. You must place a checkmark in this checkbox in the following situations:
  • The application you want to build uses VI Server references to modify a library file programmatically.
  • The application you want to build uses the Save to Library VI.
  
  If you do not enable the enhanced DSC Module Run-Time Engine in these two situations, LabVIEW returns error code 1055 when you run the built application.
  
  

Note  Enabling this option increases the file size and reduces the start-up performance of the built application.

• Use embedded version of run-time engine—(Linux) Builds the shared library using the embedded version of the run-time engine. Select this option if you want to deploy the shared library in an environment that does not require a front panel or user interface.