I'm building a deployable application that dynamically calls a number of modules uring runtime. To do this I'm aware that my dynamically called modules must be contained in either a packed library or in a subfolder that has the same relative path on the target as the development system. I've put the dynamically called modules in a library located in the root folder of the project and built my packed library from it. I have a switch in the application so that when the application is running in development mode it uses the packed library file as the root path and on the development system it uses the application folder as the root path. The application runs fine on the development system but when it runs on the taget system the dynamic calls fail. What I've found is that the VI modules stored in the packed library have their original literal file paths attached to them and so the relative path I pass to the asynchronous call I'm making fails to find the correct VI. The work around that I'm looking for is to strip the paths off the VIs stored in the packed library but I've not idea if this is the right approach or if its possible. I should add that this is the first time I've used libraries so feel free to correct any glaring errors. I've attached a jpg of the project structure as it is. Any suggestions out there please?

You could use this VI attached to get your application path. Hope this helps. Vincent

LabVIEW

Packed Project Libraries

Solved!

Author

Hi Vincent,

Just to let you know I couldn't find the solution I was looking for so I created a sub-vi that generated a modified path relative to the origianl files source path. Not at all elegant but it seems to be the solution. What it did teach me though is the need to try and use the same paths on your development systems and target machine. I've relocated the project and this has helped with other path issues I had with a device driver.

Many thanks for the help.

Simon