06-30-2015 09:22 AM
I'm a C++ developer new to LabVIEW (but living in a world of LabVIEW developers). We're using some C DLLs in our project (which I'm cross compiling for VxWorks properly) and they show up under the Dependencies folder on the target. If I manually FTP the dll over and run the project, all works great. No problem. What I want to figure out is if there's a way for the dll to automatically get deployed (i.e. copied over to the Compact RIO to the appropriate folder) automatically when I deploy the project. This seems very trivial, and yet I can't find an option to do this. I tried using a Build Specification, and it seems to put the proper files in my local directory, but the dll still never gets copied to the Compact RIO. Am I stuck with manually FTPing files over or is there a more elegant way to do this?
06-30-2015 01:32 PM
You could write a pre or post build VI that will ftp the dll for you automatically
07-01-2015 08:30 AM
I very much appreciate the thought, but don't think writing a vi with hard coded FTP parameters is all that elegant.
07-01-2015 02:23 PM
Why would they be hard coded constants? You can programmatically extract all the information you would need except for the password if one exists.
07-01-2015 02:25 PM
Ok that could be a good solution then. So in the vi I can access the target's IP address and such?
07-20-2015 08:53 AM
Another approach I have started with for the OpenG ZIP library (that will be present in the next release) is to actually create an installable RT module. That way it will show up in the installation section in MAX when selecting to install custom software to the RT target.
One complication is that the location this module needed to be copied to, is a protected location that requires elevated access rights, so I used Inno Setup to create an installer executable that requires the elevated setup rights when started.
Everything is already present in the SVN repository for the OpenG Toolkit on Sourceforge, so you can go and have a look at it.