sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-25 23:21:54 +03:00
Code
88c1b49312
samba-mirror/source4/nbt_server/wscript_build

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

55 lines
1.3 KiB
Plaintext
Raw Normal View History

s4-waf: mark the wscript files as python so vim/emacs knows how to highlight them
2010-03-28 01:48:49 +03:00
#!/usr/bin/env python
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
bld.SAMBA_SUBSYSTEM('WINSDB',
source='wins/winsdb.c wins/wins_hook.c',
autoproto='wins/winsdb_proto.h',
Introduce system MIT krb5 build with --with-system-mitkrb5 option. System MIT krb5 build also enabled by specifying --without-ad-dc When --with-system-mitkrb5 (or --withou-ad-dc) option is passed to top level configure in WAF build we are trying to detect and use system-wide MIT krb5 libraries. As result, Samba 4 DC functionality will be disabled due to the fact that it is currently impossible to implement embedded KDC server with MIT krb5. Thus, --with-system-mitkrb5/--without-ad-dc build will only produce * Samba 4 client libraries and their Python bindings * Samba 3 server (smbd, nmbd, winbindd from source3/) * Samba 3 client libraries In addition, Samba 4 DC server-specific tests will not be compiled into smbtorture. This in particular affects spoolss_win, spoolss_notify, and remote_pac rpc tests.
2012-05-21 13:45:12 +04:00
public_deps='ldb ldbsamba',
enabled=bld.AD_DC_BUILD_IS_ENABLED()
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
)
bld.SAMBA_MODULE('ldb_wins_ldb',
source='wins/wins_ldb.c',
ldb: Only build standard ldb modules when building bundled ldb.
2010-06-15 02:59:49 +04:00
subsystem='ldb',
s4-dsdb: convert the rest of the ldb modules to the new module type
2010-11-01 07:28:02 +03:00
init_function='ldb_wins_ldb_module_init',
module_init_name='ldb_init_module',
waf: Remove lib prefix from libraries manually.
2010-10-24 21:42:58 +04:00
deps='ldb netif samba-hostconfig samba-util',
wins_ldb: Build as shared library. Autobuild-User: Jelmer Vernooij <jelmer@samba.org> Autobuild-Date: Mon Oct 11 18:15:19 UTC 2010 on sn-devel-104
2010-10-11 21:32:22 +04:00
internal_module=False,
Introduce system MIT krb5 build with --with-system-mitkrb5 option. System MIT krb5 build also enabled by specifying --without-ad-dc When --with-system-mitkrb5 (or --withou-ad-dc) option is passed to top level configure in WAF build we are trying to detect and use system-wide MIT krb5 libraries. As result, Samba 4 DC functionality will be disabled due to the fact that it is currently impossible to implement embedded KDC server with MIT krb5. Thus, --with-system-mitkrb5/--without-ad-dc build will only produce * Samba 4 client libraries and their Python bindings * Samba 3 server (smbd, nmbd, winbindd from source3/) * Samba 3 client libraries In addition, Samba 4 DC server-specific tests will not be compiled into smbtorture. This in particular affects spoolss_win, spoolss_notify, and remote_pac rpc tests.
2012-05-21 13:45:12 +04:00
enabled=bld.AD_DC_BUILD_IS_ENABLED()
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
)
bld.SAMBA_SUBSYSTEM('NBTD_WINS',
source='wins/winsserver.c wins/winsclient.c wins/winswack.c wins/wins_dns_proxy.c',
autoproto='wins/winsserver_proto.h',
Introduce system MIT krb5 build with --with-system-mitkrb5 option. System MIT krb5 build also enabled by specifying --without-ad-dc When --with-system-mitkrb5 (or --withou-ad-dc) option is passed to top level configure in WAF build we are trying to detect and use system-wide MIT krb5 libraries. As result, Samba 4 DC functionality will be disabled due to the fact that it is currently impossible to implement embedded KDC server with MIT krb5. Thus, --with-system-mitkrb5/--without-ad-dc build will only produce * Samba 4 client libraries and their Python bindings * Samba 3 server (smbd, nmbd, winbindd from source3/) * Samba 3 client libraries In addition, Samba 4 DC server-specific tests will not be compiled into smbtorture. This in particular affects spoolss_win, spoolss_notify, and remote_pac rpc tests.
2012-05-21 13:45:12 +04:00
deps='cli-nbt WINSDB',
enabled=bld.AD_DC_BUILD_IS_ENABLED()
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
)
bld.SAMBA_SUBSYSTEM('NBTD_DGRAM',
source='dgram/request.c dgram/netlogon.c dgram/browse.c',
autoproto='dgram/proto.h',
s4:dsdb: Move cldap netlogon functions into samdb/ldb_modules As netlogon is handled by the samdb now, the corresponding functions should live there as well. Reviewed-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Nadezhda Ivanova <nivanova@symas.com>
2013-11-05 23:39:56 +04:00
deps='LIBCLI_DGRAM DSDB_MODULE_HELPERS',
Introduce system MIT krb5 build with --with-system-mitkrb5 option. System MIT krb5 build also enabled by specifying --without-ad-dc When --with-system-mitkrb5 (or --withou-ad-dc) option is passed to top level configure in WAF build we are trying to detect and use system-wide MIT krb5 libraries. As result, Samba 4 DC functionality will be disabled due to the fact that it is currently impossible to implement embedded KDC server with MIT krb5. Thus, --with-system-mitkrb5/--without-ad-dc build will only produce * Samba 4 client libraries and their Python bindings * Samba 3 server (smbd, nmbd, winbindd from source3/) * Samba 3 client libraries In addition, Samba 4 DC server-specific tests will not be compiled into smbtorture. This in particular affects spoolss_win, spoolss_notify, and remote_pac rpc tests.
2012-05-21 13:45:12 +04:00
enabled=bld.AD_DC_BUILD_IS_ENABLED()
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
)
bld.SAMBA_SUBSYSTEM('NBT_SERVER',
source='interfaces.c register.c query.c nodestatus.c defense.c packet.c irpc.c',
autoproto='nbt_server_proto.h',
Introduce system MIT krb5 build with --with-system-mitkrb5 option. System MIT krb5 build also enabled by specifying --without-ad-dc When --with-system-mitkrb5 (or --withou-ad-dc) option is passed to top level configure in WAF build we are trying to detect and use system-wide MIT krb5 libraries. As result, Samba 4 DC functionality will be disabled due to the fact that it is currently impossible to implement embedded KDC server with MIT krb5. Thus, --with-system-mitkrb5/--without-ad-dc build will only produce * Samba 4 client libraries and their Python bindings * Samba 3 server (smbd, nmbd, winbindd from source3/) * Samba 3 client libraries In addition, Samba 4 DC server-specific tests will not be compiled into smbtorture. This in particular affects spoolss_win, spoolss_notify, and remote_pac rpc tests.
2012-05-21 13:45:12 +04:00
deps='cli-nbt NBTD_WINS NBTD_DGRAM service',
enabled=bld.AD_DC_BUILD_IS_ENABLED()
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
)
bld.SAMBA_MODULE('service_nbtd',
source='nbt_server.c',
subsystem='service',
init_function='server_service_nbtd_init',
nbtd: Build service as shared module.
2010-11-15 14:23:46 +03:00
deps='NBT_SERVER process_model',
internal_module=False,
Introduce system MIT krb5 build with --with-system-mitkrb5 option. System MIT krb5 build also enabled by specifying --without-ad-dc When --with-system-mitkrb5 (or --withou-ad-dc) option is passed to top level configure in WAF build we are trying to detect and use system-wide MIT krb5 libraries. As result, Samba 4 DC functionality will be disabled due to the fact that it is currently impossible to implement embedded KDC server with MIT krb5. Thus, --with-system-mitkrb5/--without-ad-dc build will only produce * Samba 4 client libraries and their Python bindings * Samba 3 server (smbd, nmbd, winbindd from source3/) * Samba 3 client libraries In addition, Samba 4 DC server-specific tests will not be compiled into smbtorture. This in particular affects spoolss_win, spoolss_notify, and remote_pac rpc tests.
2012-05-21 13:45:12 +04:00
enabled=bld.AD_DC_BUILD_IS_ENABLED()
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
)
Copy Permalink