Application builder (using OpenG source)

[labmaster]

I just made a LV program and executable thing in LV8.2.0.

Only one function (for converting cluster->ini) from OpenG was used to make the program easily.

When I copy the program folder, so many OpenG (maybe related to the converting routine) codes were created in subVI folder.

My question is,

1. In distributing source code,  Is there some DLL or convenient format file for OpenG not to copy many Vis?

2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?

And as other question,

3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.

    How can I make the whole program( application+libraries installer) as small as possible?

[Jim_Kring]

If you are distributing source code, don't distribute the OpenG VIs.  Just tell your end users to install OpenG using VI Package Manager.

If you are building an EXE, there's nothing special to do, just put all of the VIs inside the EXE.

[TCPlomp]

---

@labmaster wrote:

1. In distributing source code,  Is there some DLL or convenient format file for OpenG not to copy many Vis?

2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?

And as other question,

3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.

    How can I make the whole program( application+libraries installer) as small as possible?

---

3: The DAQmx installer has several versions the smallest being 40 MB? and the largest 150 or something.
I think the VISA installer has the same options.

Ton