[omniORB] Visual Studio 2013

[Daniel Krügler]

2014-11-20 16:20 GMT+01:00 Adam Manca <darkenned at gmail.com>:
> We are using Corba but it's been some time since it was updated (using
> 4.1.3). Also the project itself is a bit older and we are considering
> upgrading to VS2013. So, to my question: does anyone have any experience
> using omniORB in VS2013 projects?

We have build OmniOrb using Visual Studio 2008 and 2012. The build
process is not trivial IMO and I would be very happy to see a
cmake-based build, but it works.

> I saw some posts about compiling it from
> the source (I did that too, used Python x86 and used the vc10 config -
> simply copied it and renamed to vc12). However, noone posted after that,
> whether it's actually working without any issues.

With OmniOrb 4.2 we stumbled across one severe issue that is described
in this posting:

http://www.omniorb-support.com/pipermail/omniorb-list/2014-November/031627.html

I have been told (search for feedback id 1033845 in the Microsoft bug
tracking system) that the mentioned incorrect behaviour of Visual
Studio that nastily interacts with the definition of the mentioned two
OmniOrb macros should be fixed in VS2013 update4. We have not the
luxury to switch to VS2013, so this is no option for us (so I strongly
hope that OmniOrb will fix the macro definitions), but if you have
this compiler you should ensure that you have at least this update
version of the compiler.

HTH & Greetings from Bremen,

Daniel Krügler