[omniORB] ANNOUNCE: omniORB 4.1 testing

[Alex Tingle]

Hi Al,

Perhaps your PYTHONPATH (environment variable) is still pointing to the 
old v4.0 omniidl backend. The 'omniidl' executable doesn't generate the 
C++ stubs itself, it calls a Python module called 'omniidl_be.cxx' 
which is usually installed into site-packages.

-Alex Tingle

--
Dammit Jim, I'm a programmer... not a mind reader!
On 26 Jan 2005, at 16:03, Al Slater wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Duncan Grisby wrote:
> |
> | Let me know if it works for you (or not).
> |
>
> Solaris 2.9, gcc 3.4.3, python 2.2
>
> I have successfuly build omniOrb 4.1 from cvs.
>
> I have installed it in a seperate directory to omniOrb 4.0.
>
> My PATH and LD_LIBRARY_PATH are set to include 4.1 but not 4.0.
>
> I am trying to build omniEvents 2.6.
>
> The stub files created by omniidl are including the following erroneous
> line which is causing compile failure.
>
> static const char* _0RL_library_version = omniORB_4_0;
>
> surely should be omniORB_4_1.
>
> I am assuming that omniidl is getting confused with the 4.0 version, 
> but
> I cannot see how. The right version _IS_ getting called ("which 
> omniidl"
> ~ reports the omniidl in the right path).
>
> Any ideas?
>
> - -- Al Slater Technical Director Stanton Consultancy
>
>
> - --
> Al Slater
>
> Technical Director
> Stanton Consultancy
> +44 (0)1273 666607
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFB979dz4fTOFL/EDYRAtdLAJ4yU2SqondlfN5c/uqcH2cdwabyuQCfTtzq
> hWVMJMpLCmbful5PQBwnSTg=
> =tRNA
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list