[omniORB] Omni Orb windows binaries only for 64 and not X86 architecture

[Olivier Thiboutot]

Hi all,

I face a very big problem....!!!!

We are using Omni orb since version 2.8 into a telephony software as the management and command part. We pilot telephony drivers of High density telephony hardware and VoIP software.

We want to move to Visual Studio 2010 since we prove the stability on other products.

Here raise my problem. For doing the job of migration, we plan steps since telephony Drivers are built for x86 core. So we cannot change the target machine to 64 bits. The package for Visual Studio contains only drivers of 64 bits target machine. I cannot rebuild Omni Orb core since we always wants to use Omni Orb default package.

Is there a simple way to correct this since conditional define into source like __WIN32__ or __x86__ looks like completely ignored.

Best regards
Olivier Thiboutot
Voxco

[Martin Ba]

Post by Olivier Thiboutot
Hi all,
I face a very big problem....!!!!
We are using Omni orb since version 2.8 into a telephony software as the management and command part. We pilot telephony drivers of High density telephony hardware and VoIP software.
We want to move to Visual Studio 2010 since we prove the stability on other products.
Here raise my problem. For doing the job of migration, we plan steps since telephony Drivers are built for x86 core. So we cannot change the target machine to 64 bits. The package for Visual Studio contains only drivers of 64 bits target machine. I cannot rebuild Omni Orb core since we always wants to use Omni Orb default package.
Is there a simple way to correct this since conditional define into source like __WIN32__ or __x86__ looks like completely ignored.

Duncan wrote (on 1st of July) for the 4.1.7 release, I quote:
:: I've only built Windows binaries for
:: omniORBpy, against Python 2.7, both
:: 32 and 64 bit. Does anyone require
:: other binaries?

So, I would read that as a statemanet that he would provide prebuilt
binaries for Windows on request.

I actually reply because I'm curious why you seem to have problems with
building omniORB yourself on Windows/VS. Are there any specfic problems?
(I mean, it's not like using the prebuilt binares saves you anything but
the build.)

cheers,
Martin

[Duncan Grisby]

Post by Olivier Thiboutot
We want to move to Visual Studio 2010 since we prove the stability on other products.
Here raise my problem. For doing the job of migration, we plan steps
since telephony Drivers are built for x86 core. So we cannot change the
target machine to 64 bits. The package for Visual Studio contains only
drivers of 64 bits target machine. I cannot rebuild Omni Orb core since
we always wants to use Omni Orb default package.

The "default" omniORB package is the source release. The Windows
binaries that I provide are just for your convenience. Given the number
of different compiler versions and sets of compiler options, it isn't
very convenient for me to build them, so with recent releases I have
tended to release in source form only.

Have you tried to build from source? It's not hard.

Cheers,

Duncan.

[Olivier Thiboutot]

Hi,

No, we never try them since binaries from package were perfect and without any problem or issue about compiler

We always try to use third party without interfering. For the build, I will have to take a machine and built it for compiling Omni since we only have Windows (Microsoft) product inside the companies. You are one of the exception we include into our solution.

Where can I find the cocking book, if it is not too complicated to point.
So the idea will be Target machine x86 Windows NT4 or more compliant, debug and release with SSL, IPV6 and IPV4,'Any' support. I think those are all basic feature but I'm not sure.

Best regards
Olivier

Post by Olivier Thiboutot
We want to move to Visual Studio 2010 since we prove the stability on other products.
Here raise my problem. For doing the job of migration, we plan steps
since telephony Drivers are built for x86 core. So we cannot change
the target machine to 64 bits. The package for Visual Studio contains
only drivers of 64 bits target machine. I cannot rebuild Omni Orb core
since we always wants to use Omni Orb default package.

The "default" omniORB package is the source release. The Windows binaries that I provide are just for your convenience. Given the number of different compiler versions and sets of compiler options, it isn't very convenient for me to build them, so with recent releases I have tended to release in source form only.

Have you tried to build from source? It's not hard.

Cheers,

Duncan.