mirror of
https://github.com/samba-team/samba.git
synced 2025-02-03 13:47:25 +03:00
500d5523d2
change was in the ldb_msg_add_*() routines, which now use the msg as a context, and thus it needs to be a talloc ptr) (This used to be commit 1a4713bfd0e519f3eb7b3241121ff914a6eeef18)
The Samba Build System ---------------------- ---------------------- Object Types ------------ the build system knows about the following object types SUBSYSTEM: a SUBSYSTEM is basicly a collection of functions, which provide an an generic API for a specific problem (e.g. libldb provides an api for gneric ldb databases. libldb_plugin provides a generic api for calling ldb plugins, so 'libldb' and 'libldb_plugin' are subsystems) MODULE: a MODULE is a specify implementation of a API provided by a SUBSYSTEM. (e.g. 'libldb_tdb' and 'libldb_ldap' are implementations of the subsystem 'libldb' API, and 'libldb_plugin_timestamp' is a module of the 'libldb_plugin' subsystem) EXT_LIB: an EXT_LIB is an external library which is needed by a SUBSYSTEM, MODULE, BINARY or LIBRARY. (e.g. 'gtk' or 'KRB5') BINARY: a BINARY means a executable binary file. (e.g. 'smbtorture' or 'ldbedit') a BINARY typicly has only commandline handling and basic functionality code in it and depends on the functions of SUBSYSTEM's (required_subsystems/REQUIRED_SUBSYSTEMS). LIBRARY: a LIBRARY means a static and/or shared library, which depends on the used OS. (e.g. for libldb 'libldb.so', 'libldb.so.0' 'libldb.so.0.0.1' and libldb.a are created on linux) a LIBRARY typicly has only glue code in it and depends on SUBSYSTEM's (required_subsystems/REQUIRED_SUBSYSTEMS). Macrodescriptions ---------------- On top of build/smb_build/public.m4 is a list of all public macros of the build system. Layout ------- Toplevel file: configure.in - included by autogen.sh: aclocal.m4 which includes the SMB_YXZ*() macros - default tests of the build system are in build/smb_build/check_*.m4 (mostly compiler and basic C type and function checks) - subsystem specific stuff should be included by 'SMB_INLUDE_M4()' Generating of 'configure' ------------------------- you need to rerun ./autogen.sh when 'configure.in' or any '.m4' file was modified, then you need to rerun configure. Generating of 'config.status' ----------------------------- you need to run ./config.status (or 'configure') after a '.mk' file was changed. Examples -------- for now please take a look at the .m4 and .mk files you find in the source tree, they should be a good reference to start. README-TODO ------------ SMB_XYZ() vs. SMB_XYZ_MK() meaning of the macros parameters and the .mk file handling examples