[omniORB] Config Option to Link omniORB Executables with omniCodeSets Library?

[Pat Pascal]

Duncan Grisby wrote:
> On Tuesday 5 December, Pat Pascal wrote:
> 
>> When building the omniORB software on Linux, is there a simple
>> configure option (or some other easy build setting) to have the
>> omniORB executables (such as omniNames) automatically link against
>> the omniCodeSets library?  I'm not familiar with the GNU makefiles,
>> and prefer not to rebuild the executables manually.
> 
> There's no configure option to do it. To do it, edit the dir.mk file in
> the omniNames directory and add $(OMNIORB_CODESETS_LIB) after
> $(CORBA_LIB_NODYN) in the libs setting at the end of the file.
> 
> Why do you want to link omniNames or other executables with the codesets
> library?
> 
> Cheers,
> 
> Duncan.

Thanks for the info.

The reason for the codesets library linking is that one of our customers 
is requesting it.  The name service names we use may contain characters 
from a non-default codeset, so they want to ensure omniNames and nameclt
handle these characters as well.  We've already linked our servers and 
clients with the codesets library, but we are using the default build 
for omniORB (which doesn't link against the codeset library).

In order to get omniNames and nameclt to handle the non-default 
codesets, is linking these executables against the codeset library the 
only thing necessary, or is something else required?

Thanks.

Pat Pascal