[omniORB] omniOrb4 - codeset intialisation exception?

[Mac]

>Does it work if you don't link with the omniCodeSets library?

Nope, i still get the exception. I also tried re-ordering the libs to try to
re-order the initialisation of the static vars, but no joy.

The next thing i could do is to code in a temporary work around which checks
to see if the codesets have been initialised, and attempts to do so if they
haven't? Maybe you could give me an estimate on your time frame for fixing
the static initialisers? If it's not for a while then i'll do my workaround.

Thanks for your help
Mac.

( ps the reason i need the codesets is for the wstring support which our app
needs )



-----Original Message-----
From: Duncan Grisby <dgrisby@uk.research.att.com>
To: Mac <mlarner@ihug.co.nz>
Cc: omniorb-list@uk.research.att.com <omniorb-list@uk.research.att.com>
Date: Monday, July 23, 2001 2:54 AM
Subject: Re: [omniORB] omniOrb4 - codeset intialisation exception?


>On Friday 20 July, "Mac" wrote:
>
>> I am using omniOrb4 ( build omniORB-20010714 ) in a win NT4.0/vs6.0
>> environment and am having a problem initializing the omniOrb4 due to
>> what appears to be some uninitialised codeset variables.
>
>[...]
>> I have included the omniCodeSets4d.lib in the project but i still must
>> be missing something??. Any ideas would be greatly appreciated.
>
>I suspect that the problem is that the current code makes invalid
>assumptions about the order that static initialisers run. Does it work
>if you don't link with the omniCodeSets library?
>
>Fixing the static initialisers is on my list of things to do.
>
>Cheers,
>
>Duncan.
>
>--
> -- Duncan Grisby  \  Research Engineer  --
>  -- AT&T Laboratories Cambridge          --
>   -- http://www.uk.research.att.com/~dpg1 --
>
>