[ome-users] Building OmeroCpp

[josh.moore at gmx.de]

Ciao, Mario & Bernhard. Having you guys around is so great!

So, to recap:

Mario Valle writes:

 > Maybe OSX is not to blame. It is entirely possible I have written a
 > malformed CPPPATH. So scons ignores it and use the default. Now I
 > cannot check, hopefully next week.

Understood. CPPPATH gets appended to the overall list of search
directories, so that sounds expected.

 > Anyway, in my opinion this is still a workaround, ICE_HOME should not be 
 > ignored by the build process.

Agreed. I assume you saw

   https://trac.openmicroscopy.org.uk/omero/ticket/1299

a fix for which has been committed. Thanks for tracking this down!

 > Bernhard Voigt wrote:
 > > I did run into the same problem. Setting the following environment
 > > vars solved compilation errors (scons recognizes those, see
 > > http://www.scons.org/doc/1.2.0/HTML/scons-user/a4774.html for a
 > > complete list)
 > >
 > > export CXXFLAGS=-Wno-error  # otherwise the deprecation warnings will
 > > cause errors
 > > export CPPPATH=/opt/Ice-3.3/include/
 > > export LIBPATH=/opt/Ice-3.3/lib64/
 > >
 > > By the way, I compile OmeroCpp on OpenSuse11.1.

These are, of course, the right flags to edit if you want to have more
control over the build. See:

  http://trac.openmicroscopy.org.uk/omero/wiki/OmeroBuild#scons

for a listing. Bernhard, could you provide me with the compilation
errors without -Wno-error?

 > >>> build:
 > >>> /omero-4.0/target/scons/scons-local-1.1.0/SCons/Platform/posix.py:38: DeprecationWarning:
 > >>> The popen2 module is deprecated.  Use the subprocess module.
 > >>>    import popen2
 > >>> /omero-4.0/target/scons/scons-local-1.1.0/SCons/Tool/msvs.py:37: DeprecationWarning: the
 > >>> md5 module is deprecated; use hashlib instead
 > >>>    import md5

These warnings are harmless, and are new in Python 2.6. I've upgraded
scons to the lastest version which I know has improvements for Python
2.6, but I don't know if these have gone away. If anyone could let me
know, that'd be great.

 > >>> I tried to:
 > >>> 1) define ICE_HOME to {ice_top_dir}
 > >>> 2) define ICE_HOME to {ice_top_dir}/cpp
 > >>> 3) run bin/omero config set ice.home {ice_top_dir}/cpp
 > >>> 4) create dist/etc/local.properties with the single line
 > >>>     ice.home={ice_top_dir}/cpp
 > >>> But the build process tries always to find Ice includes under
 > >>> /usr/share/Ice/include

Right, it was a straight-forward but unpleasant bug which should be
gone now. I'm interested, however, Mario, what order you think the
options 1 & 4 should be used in, and if you think 3 would be useful.

 > >>> Any idea? Afterwards I can contribute with the OmeroCpp build instructions...

Please! :)

Pleasant weekend everyone.
~Josh.