Age | Commit message (Collapse) | Author | Files | Lines |
|
The top level build is the official build system now.
Andrew Bartlett
|
|
Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Fri Jan 14 08:19:40 CET 2011 on sn-devel-104
|
|
This is causing problems with linker
Autobuild-User: Matthieu Patou <mat@samba.org>
Autobuild-Date: Mon Dec 13 00:25:38 CET 2010 on sn-devel-104
|
|
This is needed on openbsd as some linking flags makes mandatory to
specify the libc for the linking
|
|
dist' inclusion of configure)
|
|
This function is a wrapper around waf's check_python_header.
It avoids searching more than once for the headers bringing a small
speed improvement and a better lisibility of the logs.
But it's mainly to avoid a nasty bug when python libraries are in path
pointed by python_LIBPL (ie. /usr/local/lib/python2.6/config/) instead
of python_LIBDIR (ie. /usr/local/lib).
On the first call waf will correctly find that in order to link with
python libs it needs to add -L$python_LIBPL.
But on the next calls of check_python_headers, waf will use both the
current library path value (ie. -L/usr/local/lib/python2.6/config) and
-L$python_LIBDIR (ie. /usr/local/lib/) which will make him beleive that
python libraries are in $python_LIBDIR which at the end will make the
final link test fails in check_python_headers as it will not use the
good directory.
So by avoiding calling check_python_headers more than once we avoid
making waf fooling itself.
|
|
Autobuild-User: Matthieu Patou <mat@samba.org>
Autobuild-Date: Thu Dec 9 00:47:23 CET 2010 on sn-devel-104
|
|
use the first digit of the version number for the library version
Pair-Programmed-With: Jelmer Vernooij <jelmer@samba.org>
|
|
Autobuild-User: Matthieu Patou <mat@samba.org>
Autobuild-Date: Sat Nov 27 18:02:41 CET 2010 on sn-devel-104
|
|
if you use --git-local-changes then the version number that waf
extracts from git will have a '+' on the end if you have local
changes, as determined by running 'git diff'.
This used to be the default, but unfortunately it is far too slow on
some systems. On a NFS build system I was using the first line of
configure took about 2 minutes.
Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Tue Nov 16 01:51:54 UTC 2010 on sn-devel-104
|
|
than Bazaar revision ids.
|
|
Thanks to Tridge for pointing out what exactly I had to change. :-)
|
|
Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Thu Nov 4 22:51:06 UTC 2010 on sn-devel-104
|
|
this makes our runtime load times smaller, and also means we find bugs
that this may cause on gentoo. gentoo uses this by default
Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Wed Nov 3 00:35:56 UTC 2010 on sn-devel-104
|
|
|
|
|
|
|
|
- We don't use them anywhere (heimdal has special rules)
- They calculate the version at configure time
and may contain the wrong git hash while building
- If we really need them in future we should add them
to version.h and not config.h, as the changing git hash
will trigger a full rebuild if config.h changes.
metze
|
|
moved it out of the general waf build as the s3 waf build cannot yet
handle linking with -Wl,-no-undefined
Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Mon Oct 25 01:12:15 UTC 2010 on sn-devel-104
|
|
|
|
python3 works fine with waf fine, but our C interfaces need 2.x for
now
|
|
Guenther
|
|
thanks to ita for this
|
|
|
|
this rebuilds version.h whenever the git version changes, so we always
get the right version with samba -V. That adds about 15s to the build
time on each git commit, which shouldn't be too onerous
|
|
up in $prefix/lib.
|
|
|
|
|
|
This currently includes the source3 directory for Samba4 releases (per
past practice in mkrelease.sh), but also could include things like
DFSG-unfree RFC files in the future.
Andrew Barltett
|
|
This replaces the call to mkversion.sh in both the Samba3 and Samba4
WAF builds.
Andrew Bartlett
|
|
this is meant to be used by the s3 build, to allow jelmers work on
smbtorture4 in s3 to avoid re-running configure unless its needed
|
|
This allows for the following types of commands:
waf smbd/samba
waf smbd/server.c
waf ../lib/util/util_file.c
waf ../lib/util/util_file_*.o
this will be used as part of an updated minimal_includes.pl script
|
|
this adds a smbtorture.static binary which s3 will use in the build
farm
|
|
|
|
configure options
metze
|
|
Python 3.x is a bit fussier about print statements and indentation.
Signed-off-by: Andrew Tridgell <tridge@samba.org>
|
|
|
|
This works with both standalone lib builds and bundled builds
|
|
This should be useful for building tarballs from a clean checkout
|
|
|
|
prevent unnecessary rebuilds
|
|
|
|
these generate html documentation for the Samba python code
You need a very recent version of pydoctor
|
|
This matches what debian currently uses for libldb-samba4
|
|
|
|
|
|
If we are going to use the system versions of these libraries then
we should not force the use of the non-system headers
|
|
|
|
|
|
|