Re: Fileshare and Server Express

On Mon, 24 Sep 2007 04:27:22 -0700, umwelt@xxxxxxxxxxx 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.
.

Relevant Pages

  • called uncompiled scripts from compiled code...
    ... For some bespoke software, my client has stated that they'd like their ... engineer guys to be able to configure, and muck around with the program we ...
    (microsoft.public.dotnet.languages.csharp)
  • Fileshare and Server Express
    ... fileshare security and according to documentation, ... all the Fileshare Client modules are automatically available ...
    (comp.lang.cobol)