LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview build executable with dynamic vi's

When I build an executable with a dynamic vi located in in the support directory I will have a bunch of vi's created in that directory. For distribution all those file were also copied to the destination computer. Is there a way to hide or compress all those files on the destination computer so I can load them without the operator can see them. (without hiding the directory)

 

0 Kudos
Message 1 of 13
(3,844 Views)

Hi Poema,

 

you may try to include the "dynamic" VI in your executable instead of putting it in the data subfolder…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 13
(3,836 Views)

Hi,

 

Thanks for the tip but, that's not working for me because I am using an DLL for Pie charts.

 

0 Kudos
Message 3 of 13
(3,803 Views)

Hi Poema,

 

how is the DLL related to the VIs, which you want to hide from the user?

(You may put the VIs also in a single lvlib(p)…)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 13
(3,794 Views)

HI,

 The library I'm using is the 'DataVisualisation' tool. I have also another problem with putting the vi's in the executable. When I compile my program I am getting 'Error 6 File I/O error'.

I can put the vi in a lvlib but it is only one file the rest are dependency's.

 

0 Kudos
Message 5 of 13
(3,791 Views)

Hi Poema,

 

I can put the vi in a lvlib but it is only one file the rest are dependency's.

That's why I suggested to include that one VI into the executable. All the dependencies will be included in the exe too…

 

When I compile my program I am getting 'Error 6 File I/O error'.

Do you get that error "while compiling" or "when running the executable"?

Did you include some error logging to know which file access is failing?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 13
(3,782 Views)

@Poema wrote:
I have also another problem with putting the vi's in the executable. When I compile my program I am getting 'Error 6 File I/O error'

That sounds like an issue with how you are referencing the VIs.  Can you share some code to show how you are calling your dynamic VI?


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 7 of 13
(3,781 Views)

While compiling, there is no file name specified.

0 Kudos
Message 8 of 13
(3,776 Views)

Hi Poema,

 

is there an explorer window, pointing to the executable folder, open while compiling? Close it!

 

If this is not the case: provide more information by attaching your (full) project…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 9 of 13
(3,772 Views)

@crossrulz

FYI

When I include the vi in the program as a sub vi  I am getting 'Error 6 File I/O error' (during compilation)

When I include the vi as a dynamic vi in the executable I am getting 'Error 6 File I/O error' (during compilation)

When I include the vi as a dynamic vi in an external directory => no problem

0 Kudos
Message 10 of 13
(3,765 Views)