Missing VIs after build

7 posts / 0 new
Last post
Offline
Last seen: 2 years 10 months ago
Joined: 06/21/2017
Posts: 6
Missing VIs after build

Hello all,

I am qiute new to LabView and I have got some problem regarding with the build. The default build includes the rtilvdds.dll but when running it misses the used VIs. I tried to include one by one the used VIs but the same happens. Can someone tell me how to include to be able to move the exe to another PC?

Thank you

Ákos

Offline
Last seen: 2 months 13 hours ago
Joined: 04/23/2014
Posts: 57

Hello Ákos,

I would like to know a bit more about your environment. Which version of LabVIEW are you using? 32 or 64 bits? Are you running VIs directly or creating an .exe application from LabVIEW? Has the coputer where those files are copied installed the RTI DDS Toolkit in LabVIEW?

LabVIEW 2017, it doesn't have the RTI DDS Toolkit installed by default. It is preinstalled, so you have to use the VI Package Manager to manually install it. You can find how to do it in the section "1.2 Installing" of our Getting Started Guide: https://community.rti.com/static/documentation/dds-toolkit-labview/2.0.0.104/RTI_DDS_Toolkit_GettingStarted.pdf

Thanks,

Angel.

Offline
Last seen: 2 years 10 months ago
Joined: 06/21/2017
Posts: 6

Hi Angel,

I am using LabView 2017 32 bit and Toolkit is installed. I would like to create an .exe which is portable. So on target PC only Runtime-engine is installed.

Ákos

Offline
Last seen: 2 months 13 hours ago
Joined: 04/23/2014
Posts: 57
Hi Ákos,
 
When creating an executable LabVIEW cannot find the DDS libraries the toolkit uses: nddsc.dll, nddscore.dll and rtidlc.dll (rtimonitoring.dll and nddssecurity.dll are optional if you are using them). LabVIEW does not track dlls recursively, it considers the only libraries you are using are the ones you call in the .vi files. You can have a look at this website about that.
 
One of the things you can do it is to copy these libraries to <your .exe folder>/data (where the rtilvdds.dll should be). However this is just a workaround. The proper way of doing this is manually including them in the project so LabVIEW adds them automatically (You can find these libraries under <LabVIEW installation>\vi.lib\_RTI DDS Toolkit_internal_deps; eg C:\Program Files (x86)\National Instruments\LabVIEW 2016\vi.lib\_RTI DDS Toolkit_internal_deps). Here you have some steps how to do that:
  • Add the .dll files you need to your project. LabVIEW will not let you add them to its dependencies section. Therefore, you can create a new folder in your project to have them available for the application builder. I created one called "Dependencies". 

  • Then, when you are creating your .exe application, you need to include the library files as "Always included", in source files tab. So LabVIEW can include them automatically in the correspondent folder to run your application.

I have tried the generated stand alone application in a machine which only has the LabVIEW RunTime engine and everything was working fine. These are the files generated by LabVIEW that I have copied to the other computer:
 
Thanks,
Angel.
Offline
Last seen: 2 years 10 months ago
Joined: 06/21/2017
Posts: 6

Thank you the include of the ddls solved my problem.

Offline
Last seen: 6 years 3 months ago
Joined: 11/26/2017
Posts: 2

Where are these dll's located?

Offline
Last seen: 2 months 13 hours ago
Joined: 04/23/2014
Posts: 57

You can find these libraries under <LabVIEW installation>\vi.lib\_RTI DDS Toolkit_internal_deps (eg C:\Program Files (x86)\National Instruments\LabVIEW 2016\vi.lib\_RTI DDS Toolkit_internal_deps)