Home > Archive > Cobol > September 2007 > Fileshare and Server Express
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Fileshare and Server Express
|
|
| umwelt@hotmail.com 2007-09-24, 7:55 am |
| Hi
We're trying to amend our bespoke software application to use
fileshare security and according to documentation, we should be able
to link fhrdrpwd.o with our client application.
UNIX:
On UNIX, all the Fileshare Client modules are automatically available
so you do not need to link any extra objects when creating an
executable version of your application. However, if you want to create
a stand-alone static executable, you need to include the objects
fhrdrpwd.o and fhxscomp.o.
Unfortunately, this module doesn't appear present in Server Express
(this .o file was present in Object COBOL).
Is there an alternative to this .o?
Any help, or suggestions, would be much appreciated.
| |
| Robert 2007-09-24, 7:55 am |
| On Mon, 24 Sep 2007 04:27:22 -0700, umwelt@hotmail.com wrote:
>Hi
>
>We're trying to amend our bespoke software application to use
>fileshare security and according to documentation, we should be able
>to link fhrdrpwd.o with our client application.
>
>UNIX:
>On UNIX, all the Fileshare Client modules are automatically available
>so you do not need to link any extra objects when creating an
>executable version of your application. However, if you want to create
>a stand-alone static executable, you need to include the objects
>fhrdrpwd.o and fhxscomp.o.
>
>Unfortunately, this module doesn't appear present in Server Express
>(this .o file was present in Object COBOL).
>
>Is there an alternative to this .o?
>
>Any help, or suggestions, would be much appreciated.
You're asking how to statically link a shared library. It cannot be done.
If they supplied .a files, you can statically link them just like .o files.
You can use -L to set the library search path to . (current directory) or the directory
where your software will be installed. By doing that, you don't need to worry about being
in the end user's LD_LIBRARY_PATH.
| |
| Robert 2007-09-24, 6:56 pm |
| On Mon, 24 Sep 2007 04:27:22 -0700, umwelt@hotmail.com wrote:
>Hi
>
>We're trying to amend our bespoke software application to use
>fileshare security and according to documentation, we should be able
>to link fhrdrpwd.o with our client application.
>
>UNIX:
>On UNIX, all the Fileshare Client modules are automatically available
>so you do not need to link any extra objects when creating an
>executable version of your application. However, if you want to create
>a stand-alone static executable, you need to include the objects
>fhrdrpwd.o and fhxscomp.o.
>
>Unfortunately, this module doesn't appear present in Server Express
>(this .o file was present in Object COBOL).
>
>Is there an alternative to this .o?
>
>Any help, or suggestions, would be much appreciated.
To see which libraries your application is using, run
ldd (your executable name)
Names on the list are the ones you must distribute. They need not be in a directory named
/opt/cobol (whatever), they could be in the same directory with your executable. At
execution time, the loader finds them by searching -L and LD_LIBRARY_PATH.
LD_LIBRARY_PATH complies with the POSIX Standard and is available on every Unix. Do not
use older proprietary names such as SHLIB_PATH.
|
|
|
|
|