Michael Tokarev
2024-Jul-25 10:03 UTC
[Samba] client-only build? all internal libs statically build?
Hi! In order to test something, I tried to build smbclient and libsmbclient with all dependencies built in. My goal is to have just libsmbclient.so.0 library and smbclient executable linked with libsmbclient.so. It looks like there's no way to limit build to client only, - the build system always tries to build smbd/nmbd/etc. At the very least one can use --targets=smbclient to limit things. For static link, there's --builtin-libraries=ALL. But with this one, build immediately fails: ERROR: Target 'samba_python.cpython-311-x86_64-linux-gnu_empty_c' in directory /build/samba/python re-defined as GENERATOR - was GENERATOR I tried to find where this is defined, but as usual, wafsamba is nearly impossible to follow. Is there a way to link libsmbclient statically, without all the libsamba-private stuff? Thanks, /mjt
Reasonably Related Threads
- libsamba-policy.cpython: where it is used in samba?
- libsamba-policy.cpython: where it is used in samba?
- How to build Samba4 using static linked libraries
- Samba 4.1.4 on Solaris 10 fails linking 'default/examples/libsmbclient/teststatvfs'
- dnf-makecache.service failing every few days and dnf-automatic.service samba sssd issues (again).