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

[Pat Pascal]

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.

Thanks.

Pat Pascal

[Duncan Grisby]

Post by Pat Pascal
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.

[Pat Pascal]

Post by Duncan Grisby

Post by Pat Pascal
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

[Pat Pascal]

Post by Duncan Grisby

Post by Pat Pascal
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.

I tried your suggestion, but there was no change in the make output nor
the executable (i.e. no -lomniCodeSets4 appeared in the link command for
omniNames). I did re-run the configure script, but this also did not
produce the desired result. Is there some additional change required?

Pat Pascal

[Duncan Grisby]

Post by Pat Pascal
I tried your suggestion, but there was no change in the make output
nor the executable (i.e. no -lomniCodeSets4 appeared in the link
command for omniNames). I did re-run the configure script, but this
also did not produce the desired result. Is there some additional
change required?

Sorry, it turns out that the make rules for the autoconf build didn't
have the symbol defined. I've fixed it in CVS in the omni4_1_develop
branch.

Cheers,

Duncan.

[Duncan Grisby]

Post by Pat Pascal
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).

You shouldn't need to link omniNames with the codesets library -- just
run it using UTF-8 as its native code set using -ORBnativeCharCodeSet
UTF-8 . Generally everything can be converted to UTF-8 so that should be
sufficient.

Post by Pat Pascal
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?

If you do need to use something other than UTF-8, you should use the
same kind of nativeCharCodeSet setting to choose the one you want.

Cheers,

Duncan.