[ome-devel] Builds of OmeroCpp

[Josh Moore]

On Thu, Feb 26, 2015 at 11:13 PM, Damir Sudar <dsudar at lbl.gov> wrote:
> Hi Josh,

Hi Damir,


>>> After a couple of days of looking at OmeroCpp 5.0.8 and finding that we
>>> really do need something that can work on Windows, and we of course
>>> bumped into the error "LINK : fatal error LNK1189: library limit of 65535
>>> objects exceeded static lib". So the question: if we build OmeroCpp for
>>> 5.1-m4, how much trouble will we have connecting to a server running
>>> 5.0.8? Will basic operations such as image retrieval work?
>>
>> Highly unlikely to work at all.
>
> Bummer. So we'll have to wait on that until 5.1 is ready for production.

That shouldn't be too terribly long. We hope to freeze at the end of this
week. Then it's a matter of testing & bug fixing. As always, testing is
welcome, keeping in mind though that it's a fairly substantial DB upgrade.



>>> And the alternative to that query: is there a way to successfully build
>>> OmeroCpp 5.0.8 on Windows with a work-around for the linking issue?
>>
>> No immediate workarounds like setting some property, etc. I assume
>> your Visual Studio version requires Ice 3.5?

> Yes, we discussed whether to go down the path of Ice 3.3 (which reportedly
> creates a small enough object list) but according to ZeroC, you're then
> stuck with VS 2008 and we have a bunch of other tools and libs (e.g. Qt)
> that may or may not work with such an old Visual Studio.  So unless that's
> the only way to go, we'd like to avoid.

> In the long discussion on:
> https://trac.openmicroscopy.org.uk/ome/ticket/12229, Roger et al. figured
> out a way to split the DLL into 2 parts that appears to be implemented in
> 5.1-m4. Would there be a reasonably easy way to do a similar thing for
> 5.0.8?

We could probably list the PRs which need to be backported for this to
work on 5.0, but without taking significant focus off of getting 5.1.0 out,
there's not going to be a way we can do this work and test it properly.

If you have someone interested in giving it a try, let us know.


> Thanks,
> - Damir

All the best,
~Josh


>> On 2/24/2015 11:45 PM, Josh Moore wrote:
>>>>
>>>> Moving this somewhat progressed thread to the lists. ~J
>>>>
>>>>
>>>> On 24/02/2015 14:14, "Damir Sudar" <dsudar at lbl.gov> wrote:
>>>>
>>>> Hi Roger and Emil,
>>>>
>>>> Thanks both for the quick and very useful answers. With a good handle on
>>>> how to build (or download) the OmeroCpp package and with the very useful
>>>> simple_omero routines, we'll be able to make quick progress on our
>>>> Qt/C++ image analysis application and should be able to show that at the
>>>> Paris meeting. As Jason strongly suggested, we'll continue the
>>>> discussion about using OmeroCpp on the forum or mailing list so others
>>>> can benefit and chime in.
>>>>
>>>> The only additional pre-builts that I would like to nominate are:
>>>> - indeed Visual Studio 2013 (x64)
>>>> - Ubuntu 12.04.4 LTS and 14.04 LTS (or just 14.04 if 12.04 is too old)
>>>> - and ultimately we'll need to upgrade to MacOS 10.10 but not really
>>>> soon
>>>>
>>>> Cheers,
>>>> - Damir
>>>>
>>>>
>>>>
>>>> On 2/23/2015 4:57 PM, Roger Leigh wrote:
>>>>
>>>> Hi Damir,
>>>>
>>>> For OmeroCpp, we currently are doing builds of OmeroCpp with cmake for
>>>> several platforms:
>>>>
>>>>      https://ci.openmicroscopy.org/job/OMERO-5.1-latest-cpp/
>>>>      - CentOS 6.5, MacOS 10.8, MacOS 10.9 and FreeBSD 10.1
>>>>
>>>>      https://ci.openmicroscopy.org/job/OMERO-5.1-latest-cpp-win/
>>>>      - Visual Studio 2010 and 2012 (x64 debug)
>>>>
>>>>      Note that the coverage here is more for testing a variety of
>>>> compilers and sytems rather than for their use to end users.  The
>>>> coverage can certainly be expanded a bit for the release job, and I'd
>>>> very much like for more platforms to be supported in the form of
>>>> pre-built downloads in the medium term.  Adding a release build job for
>>>> 5.1 is needed.
>>>>
>>>> I would have like to have been able to offer this for the 5.0.x OMERO
>>>> releases as well.  Unfortunately, it wasn't possible to backport the
>>>> cmake support for 5.0 due to it breaking compatibility in a stable
>>>> release due to splitting up OmeroCpp into multiple DLLs.
>>>>
>>>> Which platforms are currently most important to you?  Is the above MSVC
>>>> Windows coverage OK, or is VS2013 also required?  Which MacOS versions
>>>> do you need?  And any particular Linux distribution versions?
>>>>
>>>> Last week we also updated our Windows Ice build to add the MSVC runtime
>>>> to the release zips.  That went up for download today:
>>>>      http://downloads.openmicroscopy.org/ice/3.5.1/
>>>>
>>>>
>>>> Kind regards,
>>>> Roger
>>>>
>>>>
>>>>
>>>> On 21/02/2015 20:25, Damir Sudar wrote:
>>>>
>>>> Hi Roger and Emil,
>>>>
>>>> With Jason visiting us yesterday and the upcoming release of 5.1 and
>>>> with us having made significant progress with our Qt/C++-based analysis
>>>> software, I'm checking in again on the status of the OmeroCpp
>>>> functionality.
>>>>
>>>> We looked at your explanations how to do builds and that appears fairly
>>>> easy. It don't suppose that pre-builds are yet available for any other
>>>> environments than CentOS 6.5, right? Will a MacOS pre-build happen as
>>>> well?
>>>>
>>>> What is the current thinking about using the Windows builds? I see there
>>>> are successful builds on Jenkins. Any chance that we will be able to use
>>>> that with 5.1?
>>>>
>>>> And then the most important question for us: will the "simple_omero cpp"
>>>> routines become available soon so we don't have to develop everything
>>>> against the raw API?
>>>>
>>>> Cheers,
>>>> - Damir
>>>>
>>>>
>>>> <clip email thread from Jul 11, 2014>