samba - Mar 2016 - Building smbclient 4.3.3 as one executable without shared libraries

When we build smbclient 4.3.3 we now have 76 shared libraries to deliver with
the smbclient binary. Is there any way to specify it statically linking the
libraries so we only have to deliver an executable ?  With 3.6.5 and 4.0.7, we
only had 3 libraries, which was more more manageable.

Thank you,
Mike Tompkins

Hi Michael,
> When we build smbclient 4.3.3 we now have 76 shared libraries to deliver
with the smbclient binary.
> Is there any way to specify it statically linking the libraries so we only
have to deliver an executable ?
> With 3.6.5 and 4.0.7, we only had 3 libraries, which was more more
manageable.

We have a --nonshared-binary= option for configure.
Which at least works in 4.4 for --nonshared-binary=smbtorture,smbd/smbd

You may want to try --nonshared-binary=client/smbclient

metze

Worked great !  Thanks !

- Mike
 
                           
-----Original Message-----
From: Stefan Metzmacher [mailto:metze at samba.org] 
Sent: Thursday, March 17, 2016 8:52 AM
To: Tompkins, Michael; samba at lists.samba.org
Cc: USA Xerox Samba
Subject: Re: Building smbclient 4.3.3 as one executable without shared libraries

Hi Michael,
> When we build smbclient 4.3.3 we now have 76 shared libraries to deliver
with the smbclient binary.
> Is there any way to specify it statically linking the libraries so we only
have to deliver an executable ?
> With 3.6.5 and 4.0.7, we only had 3 libraries, which was more more
manageable.

We have a --nonshared-binary= option for configure.
Which at least works in 4.4 for --nonshared-binary=smbtorture,smbd/smbd

You may want to try --nonshared-binary=client/smbclient

metze