sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
Code
c559e9922e
samba-mirror/source4/ntvfs/wscript_build

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

41 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
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
bld.SAMBA_LIBRARY('ntvfs',
source='ntvfs_base.c ntvfs_generic.c ntvfs_interface.c ntvfs_util.c',
autoproto='ntvfs_proto.h',
deps='tevent samba-modules',
private_library=True,
build: Build less of Samba when building --without-ntvfs-fileserver We would build, but not use, many components of the NTVFS file server even when we asked not to. They would then consume disk, but not be of any use Signed-off-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Garming Sam <garming@catalyst.net.nz>
2016-05-10 20:33:17 +03:00
enabled=bld.CONFIG_SET('WITH_NTVFS_FILESERVER')
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
)
build: Build less of Samba when building --without-ntvfs-fileserver We would build, but not use, many components of the NTVFS file server even when we asked not to. They would then consume disk, but not be of any use Signed-off-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Garming Sam <garming@catalyst.net.nz>
2016-05-10 20:33:17 +03:00
bld.RECURSE('posix')
if bld.CONFIG_SET('WITH_NTVFS_FILESERVER'):
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
bld.RECURSE('common')
bld.RECURSE('unixuid')
bld.RECURSE('sysdep')
build: commit all the waf build files in the tree
2010-03-17 14:07:42 +03:00
build: Build less of Samba when building --without-ntvfs-fileserver We would build, but not use, many components of the NTVFS file server even when we asked not to. They would then consume disk, but not be of any use Signed-off-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Garming Sam <garming@catalyst.net.nz>
2016-05-10 20:33:17 +03:00
bld.SAMBA_MODULE('ntvfs_cifs',
source='cifs/vfs_cifs.c',
subsystem='ntvfs',
init_function='ntvfs_cifs_init',
deps='LIBCLI_SMB smbclient-raw param_options'
)
bld.SAMBA_MODULE('ntvfs_simple',
source='simple/vfs_simple.c simple/svfs_util.c',
autoproto='simple/proto.h',
subsystem='ntvfs',
init_function='ntvfs_simple_init',
deps='talloc'
)
bld.SAMBA_MODULE('ntvfs_ipc',
source='ipc/vfs_ipc.c ipc/ipc_rap.c ipc/rap_server.c',
autoproto='ipc/proto.h',
subsystem='ntvfs',
init_function='ntvfs_ipc_init',
deps='NDR_NAMED_PIPE_AUTH npa_tstream gssapi samba-credentials DCERPC_SHARE'
)
Copy Permalink