[ome-devel] building omero cpp ice on windows

[josh.moore at gmx.de]

Hi Bernhard, Mario, et al.

Mario Valle writes:
 > 300MB?

Unfortunately, yes. The libraries on Windows are *very* large.

 > On Mac OSX 10.4 the libraries are:
 > cd omero-cpp/Beta3.2/dist/lib
 > ls -l *.d*
 > -rw-r--r--   1 mvalle  mvalle  35291724 Jan 13 14:10 libOMERO_client.0.dylib
 > -rw-r--r--   1 mvalle  mvalle     17304 Jan 13 14:10 libOMERO_common.0.dylib
 > -rw-r--r--   1 mvalle  mvalle    405488 Jan 13 14:11 
 > libOMERO_licenses.0.dylib
 > 
 > Are you sure they are not compiled debug?
 > Hope it helps!
 >                    mario
 > 
 > Bernhard Voigt wrote:
 > > hi all!
 > >
 > > i will need a windows build of the ice/cpp omero library. i could get 
 > > it going using the generated sources from the linux build of 
 > > omero-cpp. i just copied all header and cpp files from 
 > > components/tools/OmeroCpp/{src,target} and put them into folders omero 
 > > and omero/model. the build with Visual Studio 2008 went quite
 > > well, 

Good to hear.

 > > with minor hickups eg. client.cpp uses long types, these should be 
 > > Ice::Long or Ice::Int64 to be platform independent.

Thanks for this. Can you give me the compiler error message?

 > > howerver, the resulting lib is roughly 300MB and that's not really 
 > > convenient to work with. before i start looking into splitting this 
 > > library into several bits, i wanted to whether the will be an official 
 > > windows build of the cpp client libs for windows in the near future?

"Official" in terms of providing DLLs is not a top priority for the
open-source project because of the sheer effort it takes to cover all
the bases. This is something we'd obviously be interested in
everyone's feedback on, but for 4.0 it is unlikely that we will have
the necessary resources.

 That being said, we very much want the C++ build to be fully
supported and will be testing that on the platforms we
have. Obviously, your mileage may vary. (One issue, for example, will
be that for our configuration including IcePy, ZeroC only supports
Visual Studio 2005.)

 > > by the way, is it at all ossible to split the lib into parts and only 
 > > use a small fraction? e.g. if i'm only accessing a few classes like 
 > > the services, image, experimenter,... can i only compile and link 
 > > those into a small lib and link against this?

Theoretically it should be possible, though it may be necessary for us
to add some forward definitions to the code generation. If you try to
go down this path, please keep us posted.

 > > thanks! bernhard

Very welcome.
~Josh.