Age | Commit message (Collapse) | Author | Files | Lines |
|
this lets the s3 waf build use "make help"
Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Wed Dec 1 01:47:50 CET 2010 on sn-devel-104
|
|
|
|
I finally worked out the GNU make syntax for this
|
|
on PPC64 Linux systems a 'S' line from nm means "small object
uninitialised data"
|
|
metze
|
|
waf wrapper
You can to do thinks like this now:
make test TEST_OPTIONS="--valgrind-server" TESTS=wbinfo
metze
|
|
I'm still too addicted to this as my standard debugging environment, and while I can learn the new command, this helps the muscle-memory.
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
|
|
|
|
We don't want configure in the build farm to show green when it fails
|
|
|
|
this cleans up the more than rm -rf bin
|
|
The waf build now checks for all A=B variables passed via make
and sets the same waf internal variable. This means all waf options
are available via make.
Removing this from the Makefile makes us less reliant on a modern
version of make.
Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
|
|
This is needed for symbols like tdb_null in tdb, which are part
of the public ABI
Pair-Programmed-With: Rusty Russell <rusty@samba.org>
|
|
the first column varies in length for different architectures
|
|
|
|
This means "make -j" and "make -k" now do roughly what is expected
make -j will use the number of CPUs on the system, regardless of the
number after the -j (as MAKEFLAGS doesn't contain that value).
make -k will will continue on errors
|
|
|
|
the symlink will get updated with the right target when waf dist is
used in each directory
|
|
This hopefully fixes the build on MacOS 10.
metze
|
|
Bug: https://bugzilla.samba.org/show_bug.cgi?id=4081
With this patch we are able to invoke s4 builds from the outside of the
"source4" directory (but the target remains the "source4/bin" path).
One constraint: all commands: "autogen-waf.sh", "configure", "make" have to be
run from the same directory!
Regarding "make": you have to run it using "make -C <source4 path> [targets]" if
the invoke directory is not "source4" itself.
|
|
|
|
|
|
this one will work with the tdb, talloc, etc directories
|