diff options
author | Michael Adam <obnox@samba.org> | 2011-04-02 02:20:49 +0200 |
---|---|---|
committer | Michael Adam <obnox@samba.org> | 2011-04-02 03:26:55 +0200 |
commit | d143bc444c10df99b2dd64f4a0e02c902c3c024e (patch) | |
tree | a5aaf407ae32843337584ed1362031140649cec7 /script/bisect-test.py | |
parent | af82dcae302934c4ea9c14a5932a4647444f0a63 (diff) | |
download | samba-d143bc444c10df99b2dd64f4a0e02c902c3c024e.tar.gz samba-d143bc444c10df99b2dd64f4a0e02c902c3c024e.tar.bz2 samba-d143bc444c10df99b2dd64f4a0e02c902c3c024e.zip |
s3:waf: add cluster support / ctdb checks.
The checks are roughtly taken from the autoconf ctdb checks.
I was not able to implement checks with CHECK_DECL, CHECK_TYPE,
CHECK_HEADER and friends, because the ctdb headers seem to need too
special a setup of includes and defines in order to compile.
So I used CHECK_CODE() in all checks.
In the long run, this should be changed.
I supported a --with-ctdb-dir options to allow for building
against a ctdb that is not installed into /usr (e.g. against
a local git checkout). In order to implement this, I had to
hand includes in to the CHECK_CODE function.
Here I found a problem with CHECK_CODE (or even the core waf
conf.check() function: The CHECK_CODE function does not
expand the includes it gets (i.e. '#' is not expanded to the
base dir, and relative paths are left relative). But the core
check() function seems to ignore all include paths that are
not absolute paths. Hence in particular the usual default '# .'
for the includes is useless. So I preprocessed the list of includes
for the cluster checks. But I assume that it would be useful
to move this expansion into CHECK_CODE or even into the core
waf check function.
Autobuild-User: Michael Adam <obnox@samba.org>
Autobuild-Date: Sat Apr 2 03:26:55 CEST 2011 on sn-devel-104
Diffstat (limited to 'script/bisect-test.py')
0 files changed, 0 insertions, 0 deletions