LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

build application with 3rd party net Omnidriver dependency included

Hello there, i am new in building installer with labview expecially using 3rd party software like omnidriver from ocean optics. So here's the thing, can anyone guide me to clean and proper way for building application that includes netomnidriver.dll? Whenever i install to other computer, it shows broken arrows and i assume that labview did not include all dependencies. It can only be solved if i install the whole omnidriver cd to the other computer to make it running. I am using labview 2013, windows 7. Can anyone pro's out here help me in this one. Appreciated.

0 Kudos
Message 1 of 11
(3,965 Views)
If you are using an external DLL, the builder should include it automatically. Does the DLL show up in the build when you do a preview? It sounds like there may be a dependency that LabVIEW isn't catching. If you could get from the vendor a list of all the support files that are needed you could include them individually.

What do you mean it shows broken arrows? Executables don't show broken arrows.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 11
(3,927 Views)

Hello Mike,

Thank for replying. Yes the dll shows in the preview. However, i believe when installing the omindriver cd, it includes something to do with net registry.Correct me if i am wrong, I think the labview builder did not include the registry dependancy as well. i think this is the problem. How the best way to include all, any succseful documentation, tutorial would help.

 

It is not the executables are broken, just the application cannot run because of missing dependancies. 

 

Thanks

 

El Gringo the Magico

0 Kudos
Message 3 of 11
(3,914 Views)
This is where my recommendation to talk to the vendor comes in. They can tell you what is missing and if it is a case of a missing registry entry, the installer can write to the registry.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 4 of 11
(3,910 Views)
You might also want to check that product to see if they have a support forum. My gut tells me you are not the first person to run into this.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 5 of 11
(3,908 Views)

That could be one of the idea. Besides that, is there any good software that can the tell the registry depenedancies? let say like dependancy walker? or any add-on from labview software?

Thanks

 

El Gringo the Magico

0 Kudos
Message 6 of 11
(3,906 Views)
No, on both counts ... at least as far as I have heard.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 7 of 11
(3,901 Views)

So you're saying that building application with labview will not automatically add the registry entry somehow.  

0 Kudos
Message 8 of 11
(3,879 Views)
Right, how is LabVIEW to know what is needed?

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 9 of 11
(3,869 Views)
It is the installer that you need to focus on. Just like building an installer with NI drivers such as DAQmx, you need to include the third-party installer. Simply building an exe does not include any external files such as a dll.
Message 10 of 11
(3,859 Views)