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

Creating a Build Specification (Windows CE, Touch Panel Module)

LabVIEW 8.6 Touch Panel Module Help
June 2008

NI Part Number:
372507A-01

»View Product Info

You must create a build specification to build a Touch Panel VI into an application. Complete the following steps to create a build specification.

  1. Right-click Build Specifications in the Project Explorer window and select New»Touch Panel Application (EXE) from the shortcut menu to open the Touch Panel Build Specification Properties dialog box.
  2. Define the settings for the Touch Panel application.
    1. Enter a name for the build specification in the Build specification name text box, which is the name that appears in the Project Explorer window.
    2. By default, the name of the application is the same as the top-level VI. If you do not want to use the top-level VI name for the application name, remove the checkmark from the Same as top-level VI checkbox.
    3. (Optional) Enter the name of the application on the target in the Target filename text box if you are not using the top-level VI name.
    4. Browse to and select the destination directory of the application on the host computer in the Destination directory path control.
    5. Enter the destination directory of the application on the target in the Remote path for target application text box.
    6. (Optional) Place a checkmark in the Generate serial only checkbox if you want to treat the Touch Panel VI as if it were assigned a subroutine priority and execute parallel loops serially, which results in a smaller, faster application.
    7. (Optional) Place a checkmark in the Enable debugging checkbox if you want to enable debugging in the application. This option generates extra debugging information and makes the application larger.
    8. (Optional) Place a checkmark in the Expression folding checkbox if you want to enable expression folding. This option generates better performing and more efficient code by collapsing groups of nodes into single expressions.
    9. (Optional) Enter the front panel scale factor in the Front panel scale factor text box. The default is 2. The front panel scale factor determines how LabVIEW resizes front panel objects when you build the Touch Panel VI into an application. When you build the application using the default front panel scale factor, LabVIEW reduces the user interface by a scale factor of two, so fonts appear as 14-point type and the user interface is 240 x 300 pixels or 300 x 240, depending on the orientation.
    10. (Optional) Select the depth for the bitmap you want to generate in the Screen depth list. The default is 8, which means LabVIEW generates 8-bit bitmaps when you build a Touch Panel VI that includes pictures into an application. You can generate 8-, 16-, or 24-bit bitmaps.
    11. (Optional) Select how you want to allocate memory for array, cluster, string, variant, and waveform constants from the Allocate constants pull-down menu. The default is First Use, which allocates memory the first time you use constants on the block diagram.
    12. (Optional) Select how you want to free memory resources for array, cluster, string, variant, and waveform constants from the Deallocate constants pull-down menu. The default is Out of Scope, which frees memory resources when constants are no longer used.
  3. Select the Device Information category to view which target this build specification applies to.
  4. Select the processor for the target. You can select only the processors that are compatible with the current build specification.
  5. Select the Source Files category to select the source files to include when you build the Touch Panel VI into an application.
    1. Select the top-level VI for the application and click the blue arrow button to move the VI to the Top-level VI text box. Touch Panel VIs can have only one top-level VI.
    2. Select any additional files for the application and click the blue arrow button to move the files to the Additional files list. You can add .c, .lib, .obj, and .cpp files.
    3. Select any dynamic VIs to include in the application, even if the the top-level VI does not contain references to the files, and click the blue arrow button to move the VIs to the Always Included list.
  6. (Optional) Select the Source Files Settings category if you want to set VI-level C Code generation options. You must select a VI to see the code generation options.
  7. (Optional) Select the Machine Aliases category if you are using shared variables and are building an application for multiple Touch Panel targets. The Machine Aliases category lists targets in the project that support hosting shared variables. Touch Panel targets do not support hosting shared variables. Use the Machine Aliases category to overwrite the default IP address of the shared variable host target so you can move the shared variable to a different host without rebuilding the application.
    1. (Optional) If you need to change the IP address of the shared variable host, select the IP address in the Address list.
    2. (Optional) Enter the correct IP address of the shared variable host.
    3. (Optional) Place a checkmark in the Deploy aliases file checkbox if you want to create the aliases file when you build the VI into an application and deploy the aliases file when you deploy the application to the target.
      Note  You must create and deploy the aliases file manually if you do not place a checkmark in the Deploy aliases file checkbox. If you are using a target that eMbedded Visual Tools enables, you must manually create and deploy the aliases file.
  8. Select the Generated Files category to view the application filename that this build specification creates. The aliases file also is listed if you placed a checkmark in the Deploy aliases file checkbox on the Machine Aliases page.
  9. Click the OK button.

After you create the build specification you can build the VI into an application.


Resources


 

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