Framework developed by the LevyLab research group at the University of Pittsburgh.
An Instrument developed using this framework will have access to the following capabilities:
Instrument Framework makes extensive use of JKI State Machines and JKI State Machine Objects.
The following files and folders are created from the Instrument Framework Template:
Instrument X\ :: Project Root
Instrument X\build support\ :: Files used to build VIP and EXE
Instrument X\lvsrc\ :: Instrument X.lvproj and all other LabVIEW code goes here
Instrument X\.gitattributes :: Tell git to treat certain text files as if they are binary
Instrument X\.gitignore :: Tell git which files and folders to ignore
Instrument X\LICENSE :: LICENSE file. Default is BSD-3 Clause
Instrument X\README.md :: Your project README
When you are ready to build your project into a VI package, EXE application, or a self-extracting installer, there are a few things to keep in mind.
The following folders are not created by the Template (because they are initially empty folders), but they are important for building to run smoothly.
Instrument X\builds :: builds root
Instrument X\builds\7z Install
Instrument X\builds\Application :: Application (exe) Destination Directory
Instrument X\builds\Installer :: Installer Destination Directory
Instrument X\builds\Latest
Instrument X\builds\Package :: VIPB Build Output Directory
It is important to define and use canonical name for your project right away. In this tutorial I am calling it Instrument X. This is important when setting up your build spec files:
"Product Name" = "Instrument X"
"Build Output" = "Instrument X\builds\Package"
"Build specification name" = "Instrument X Application"
"Application (exe) Destination" = "Instrument X\builds\Application"
"Build specification name" = "Instrument X Installer"
"Installer Destination" = "Instrument X\builds\Installer"
Please read the documentation.
Please contact Patrick Irvin