Open Microscopy Environment

Hello everybody,

We would like to develop a client application in labview to communicate with OMERO server (read/write images and metadata). We was wondering if:

- is it strictly necessary to compile OMERO server again in order to develop the client ?? This topic is not clear for us.
- is there anyone who has recently developed a .dll in C++ that we can try to integrate in labview ?

Thank you in advance.
Regards.

leonardo.lo wrote:Hello everybody,

Hi,

We would like to develop a client application in labview to communicate with OMERO server (read/write images and metadata). We was wondering if:

- is it strictly necessary to compile OMERO server again in order to develop the client ?? This topic is not clear for us.

Not exactly, no. The part of the build system that generates the .ice files will be needed for the code-generation step in C++. But the client library itself need to be compiled against the server. The C++ bindings from the client will communicate with the Java bindings of the server via a binary protocol.

- is there anyone who has recently developed a .dll in C++ that we can try to integrate in labview ?

We do have some development builds for C++: see https://ci.openmicroscopy.org/job/OMERO-5.1-merge-cpp-win/ -- what platform(s) are you looking for?

~Josh.

jmoore wrote:We do have some development builds for C++: see https://ci.openmicroscopy.org/job/OMERO-5.1-merge-cpp-win/ -- what platform(s) are you looking for?

I was looking for .dll in windows 7 64bit sp1 platform

And which Visual Studio version? Does LabView have any other dependencies? Debug v. Release?

Cheers,
~Josh.

jmoore wrote:And which Visual Studio version? Does LabView have any other dependencies? Debug v. Release?

I've installed Visual Studio 2015, but I could also downgrade to 2013 (64 bit) if it's necessary.
About Labview I think the only bound is 64bit, infact our intention is to develop a .dll in Visual Studio that can be called from Labview in order to communicate with OMERO.

Visual Studio 2015 isn't currently tested or supported. This is due to the fact that Ice 3.4 and 3.5 do not have builds available for this Visual Studio version. It might be possible to hand-build your own Ice with VS2015, but this is untested by ourselves, nor have we yet tested if our own code works with VS2015. Ice 3.6.1, released two weeks ago, does support VS2015, and so once we support Ice 3.6, we can then support Visual Studio 2015 properly, both by having it VS2015 being tested with our CI infrastructure and by providing 2015 builds for download. In summary, Ice 3.6 is the blocking issue here. However, Ice 3.6 is not supported by our current 5.1.x releases, and is unlikely to be supported in the upcoming 5.2.x releases either due to other features taking higher priority. It is likely that it will be supported in our following 5.3.x/6.0.x releases next year.

In the meantime, VS2013 will certainly work and it can be installed in parallel with VS2015.

Kind regards,
Roger Leigh