You are here: NI Home > Support > Product Reference > Manuals > LabVIEW Microprocessor SDK 2.5 Help

You do not need to be familiar with the entire labview directory structure, but you need to be aware of the following directories:

• autotest—Contains the embedded autotest framework and test VIs. The tests you run as part of the embedded autotests are in the tests\Large semi-auto tests subdirectory.
• CCodeGen—Contains FuncList.dat and the following subdirectories:
  • analysis—Contains the source for the analysis library.
  • build—Contains build scripts and makefiles. The Unix Console target is the only example target in this directory. The build scripts and the makefiles for the other embedded targets are located in the labview\Targets\NI\Embedded directory.
  • Include—Contains the include files for the run-time library. This directory contains several subdirectories, but the \os subdirectory is the directory you need to be familiar with.
    • os—Contains subfolders for the operating systems the example targets use. Each subfolder contains only header files. Do not put C files in this directory. Instead, put the associated C files in the labview\CCodeGen\libsrc\os directory.
  • libsrc—Contains the same directory structure as the \Include subdirectory. Like the \Include subdirectory, this directory contains several subdirectories, but the \os subdirectory is the directory you need to be familiar with.
    • os—Contains subfolders for the operating systems the example targets use. Each subfolder contains only C files. Do not put header files in this directory. Instead, put the associated header files in the labview\CCodeGen\Include\os directory.
  • examples—Contains examples. The \lvemb subdirectory contains some embedded-specific examples for working with interrupts and the Inline C Node.
  • help—Contains help files.
  • manuals—Contains documentation in PDF format.
  • readme—Contains readme files for LabVIEW and any additional modules or toolkits.
  • Targets\NI\Embedded—Contains the target directory folders for NI embedded targets. The target directory organizes targets into a hierarchy for greater reuse of target implementation code. This hierarchy organizes targets by operating systems. The Embedded Development Module target implementations–which contain the plug-in VIs, libraries, helper scripts, and other files required to implement a target–are located in this directory. The target directory hierarchy is OS-centric and supports subtargeting. The top-level targets are self-contained and do not rely on any subtarget implementations below the subtarget. In contrast, the subtargets rely on the top-level target implementation.
    • eio—Contains Elemental I/O implementations for embedded targets.

      Note  LabVIEW does not recognize targets outside of the labview\Targets\< company name >\Embedded directory. You must have an Embedded subdirectory under your company name directory.

• vi.lib—Contains libraries of built-in VIs. You need to be familiar with the following subdirectories:
  • Embedded—Contains VIs that run on the target when a user builds an embedded VI into an embedded application. Use this directory for the VIs you want to add to the Functions palette. Create a subdirectory for your target.
  • LabVIEW Targets\Embedded—Contains the plug-in VIs and any utility or helper VIs. The VIs in this directory are not intended to be on the Functions palette or used by end users.