8.x LabVIEW Linker

Introduction
OpenG Builder uses the LabVIEW linker to retrieve info on the VIs that needs to be included in the build.

Changes in linker info
LabVIEW 8.x introduced an extended set of possible file types. To be able to fully deal with the possibilities of the new file types (libraries/classes) we need to adjust OpenG builder to use the new linker info. For OpenG Builder 2.0 there was a simple conversion between linker 7.x filetypes and 8.x filetypes:

As you can see the OpenG 2.0 list is rather short, another interesting observation is that the LabVIEW linker info has expanded between 8.2 and 8.6. NI has chosen wisely to add the new types to the end of the list, between 6.x and 8.x the linker type has been shuffled. Ideally we would use the same enum for OpenG as LabVIEW does.

Where do we use linker info?
When we read info on the files used inside the project
 * All VIs button on the Source VIs tab
 * On the VI properties page we read the type of the VIs
 * When OGB checks the linking of a project
 * When we start to build OGB
 * When we end a build in OGB

Where don't we use the linker info
In the API (luckily).

Conclusion
Changing the OpenG 2.0 types to match with the latest LabVIEW linker info (currently 8.6) will most likely have no impact on external code (Callback VIs, Pre-Post Build VIs)