mirror of
https://github.com/samba-team/samba.git
synced 2024-12-24 21:34:56 +03:00
f3862b9171
Don't expose a libccan.so; it would produce clashes if someone else does the same thing. Unfortunately, if we just change it from a SAMBA_LIBRARY to a SAMBA_SUBSYSTEM, it doesn't create a static library as we'd like, but links all the object files in. This means we get many duplicates (eg. everyone gets a copy of tally, even though only ntdb wants it). So, the solution is twofold: 1) Make the ccan modules separate. 2) Make the ccan modules SAMBA_SUBSYSTEMs not SAMBA_LIBRARYs so we don't build shared libraries which we can't share. 3) Make the places which uses ccan explicit. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Autobuild-User(master): Rusty Russell <rusty@rustcorp.com.au> Autobuild-Date(master): Fri Jun 29 06:22:44 CEST 2012 on sn-devel-104
17 lines
335 B
Python
17 lines
335 B
Python
#!/usr/bin/env python
|
|
|
|
import Options
|
|
|
|
def set_options(opt):
|
|
opt.RECURSE('lib/tdb')
|
|
|
|
def configure(conf):
|
|
conf.RECURSE('lib/tdb')
|
|
|
|
def build(bld):
|
|
bld.RECURSE('lib/tdb')
|
|
bld.SAMBA_LIBRARY('tdb_compat',
|
|
source='tdb_compat.c',
|
|
deps='replace tdb',
|
|
private_library=True)
|