Hi Matt,
1. Can openjava be used to satisfy jni inclusion or does it have to be the commercial variety? Has openjava been tested?
Yes, both the public and our internal V5.5.0 release is built with openjava.
2. Motif is available, and I verified that it can be found on one install test, so I assume it compiles. I have no need of it.
By default Proview is built with GTK, but it is still possible to build with Motif, although the Motif version hasn't been updated for long and the functionality is limited. When building with Motif, motif is specified in the build command. Otherwise this module is not required.
3. hdf5 seems to be looking for openmpi. The file mpi.h.no is not something I'm familiar with (and I have some contact with openmpi). I can't seem to find that in any of the openmpi packages. Can you instruct me as to where this comes from?
It's in libopenmpi-dev.
4. mq/wmq: If understand correctly these are message brokers for other software. I don't have enough information to go on, but one looks like it is for websphere, and I don't currently have access.
Yes, wmq is websphere, and mq is a Linux version of PAMS/DMQ once from Digital Equipment. We still use it but no one else seems to know anything about it.
5. Profinet: Don't have access, and I'd love to have access.
Good luck.
6. Powerlink: This I can install/check/and test *if* openpowerlink is an acceptable replacement for powerlink?
It is openpowerlink that you should use.
7. libpcap: UPDATE done (from standard packages)
Only needed if Powerlink is used.
8. CIFX: I don't have access. I may end up purchasing these cards, so this may change.
We made an interface to this card as an alternative to the Softing Profinet stack. As the Softing stack worked well we haven't tested the Hischer CIFX card since then (eight years ago). Now there is a cheap mini version of CIFX, NetHat, for Rasberry Pi that would be interesting to test.
9. libnodave: UPDATE: is found and works (from source, no package exists)
10. Can you explain why powerlink is being looked at again, this second time (same for mq/wmq)?
There is one for inlcude files and one for archives. The reason is to find the path to the include file for the compiler, and the path to the archive for the linker.
11. Android: I would like to eventually do this, but this needs to be low priority for me, as we cannot use mobile devices with our system.
The Android app is still an Eclipse project and probably has to be migrated to Android Studio before it can be built on newer releases.
/Claes