I've downloaded the bindings. The README says to install via the JKI Package Manager, which I downloaded, but zmq is not listed. The zmq bindings download page indicates the file is a VIP, but the actual file is a ZIP, which the JKI Package Manager does not recognize. I can run the PostInstall.vi in labview without errors, but when I try to load any of the examples, I get numerous missing symbols or "subVI not executable" errors.
I'm trying to get a linux application to communicate to labview, and zmq looks most promising, but only if I can get it to actually work. Thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually the VIP file is just a fancy ZIP file; but unless it's .VIP then VIPM may not recognise it- so make sure it hasn't been renamed. The installation process is required to update paths and dependencies, so just manually calling PostInstall will not work.
Check the file extension, and if it's still not working, post your distro details and LabVIEW+VIPM versions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running LabView 2013 and JKI VIPM version 2013.0.1 build 1905.
I'm loading ZeroMQ v3.1.0.93. The VIPM indicates that the install is successful.
When I attempt to load any of the examples, I get a missing DLL error (about 20 of them) and the run arrow show about 20 missing symbols (all zmq related). I have NOT run the PostInstall.vi manually. Thoughts? The specific error is:
This application has failed to start because MSVCP110.dll was not found. Re-installing the application may fix this problem.
P.S. This is the same type of error I was getting before.
Last edit: mark 2014-02-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is because I was using the pre-compiled version of libzmq. In the next release I'll be recompiling it myself in Visual-C++ 2010, which does not require a separate run-time as it comes with LabVIEW.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've downloaded the bindings. The README says to install via the JKI Package Manager, which I downloaded, but zmq is not listed. The zmq bindings download page indicates the file is a VIP, but the actual file is a ZIP, which the JKI Package Manager does not recognize. I can run the PostInstall.vi in labview without errors, but when I try to load any of the examples, I get numerous missing symbols or "subVI not executable" errors.
I'm trying to get a linux application to communicate to labview, and zmq looks most promising, but only if I can get it to actually work. Thoughts?
Actually the VIP file is just a fancy ZIP file; but unless it's .VIP then VIPM may not recognise it- so make sure it hasn't been renamed. The installation process is required to update paths and dependencies, so just manually calling PostInstall will not work.
Check the file extension, and if it's still not working, post your distro details and LabVIEW+VIPM versions.
I'm running LabView 2013 and JKI VIPM version 2013.0.1 build 1905.
I'm loading ZeroMQ v3.1.0.93. The VIPM indicates that the install is successful.
When I attempt to load any of the examples, I get a missing DLL error (about 20 of them) and the run arrow show about 20 missing symbols (all zmq related). I have NOT run the PostInstall.vi manually. Thoughts? The specific error is:
This application has failed to start because MSVCP110.dll was not found. Re-installing the application may fix this problem.
P.S. This is the same type of error I was getting before.
Last edit: mark 2014-02-26
Sorry, based on your post I thought you were installing under Linux. The missing DLL is the Visual-C++ 2012 run-time, which can be downloaded from Microsoft http://www.microsoft.com/en-us/download/details.aspx?id=30679
This is because I was using the pre-compiled version of libzmq. In the next release I'll be recompiling it myself in Visual-C++ 2010, which does not require a separate run-time as it comes with LabVIEW.