BUILDING SAMBA 4.0
-(which build system to use and why)
===================================
The waf build
will use our internal version of Heimdal). Please note that builds
with MIT krb5 support will not have AD DC features.
-By the time of the first release candidate, we will finish renaming
-the binaries that we ship so that where we provide a tool under a name
-that was used in Samba 3.x, it continues to behave in the same way it
-always has. This will ensure that our change in build system does not
-impact on our user's ability to use Samba as they always have.
+Where we provide a tool under a name that was used in Samba 3.x, it
+continues to behave in the same way it always has. This will ensure
+that our change in build system does not impact on our user's ability
+to use Samba as they always have.
For developers, this build system backs a comprehensive 'make test',
which provides code coverage of around 48% of our code by line:
The autoconf build
------------------
-For a small number of users, the requirement to have access to Python
-2.4 and perl will be unacceptable, and for these users we continue to
-provide the 'autoconf' build system used in Samba 3.x under the
-source3/. This will build fewer parts of Samba, but should not be seen
-as 'the file server build' (typical file server deployments should use
-the top level build), but as a measure provided with limited features
-for systems and organisations unable to meet the requirements for the
-new build system.
-
-If you do need to use the autoconf build system, please let us know:
-both why you cannot use the 'waf' build in the top level, and what
-features of the source3 build that you require. We need this
-information to assess the continuing demand for this parallel
-infrastructure, and to determine which features need to remain available
-in both build systems.
+The autoconf build was removed in Samba 4.1. If you have tried and
+failed to use our waf build system, you may wish to use the latest
+supported 4.0 release instead, while we address your use case.
Optional Libraries
------------------
To assist users and distributors to build Samba with the full feature
-set, by the first release candidate the build system will abort if our
-dependent libraries and their header files are not found on the target
-system. This will mean for example, that xattr, acl and ldap headers
-must be installed for the default build to complete. The configure
-system will check for these headers, and the error message will
-indicate:
- - the required header and library
- - the option (such as --without-acl-support) that can be specified to
- skip this requirement, and
- - the feature (ACL support optional for file servers, mandatory for AD
- Domain Controller) being skipped.
+set, the build system will abort if our dependent libraries and their
+header files are not found on the target system. This will mean for
+example, that xattr, acl and ldap headers must be installed for the
+default build to complete. The configure system will check for these
+headers, and the error message will indicate the option (such as
+--without-acl-support) that can be specified to skip this requirement.
This will assist users and in particular distributors in building fully
functional packages, while allowing those on systems truly without these
-facilities to continue to build Samba after careful consideration.
+facilities to continue to build Samba after careful consideration.
+
+This feature is not currently supported for xattr.
git.samba.org / vlendec / samba-autobuild / .git / blobdiff