proposal: merge waf build of s4 to master

Volker Lendecke Volker.Lendecke at SerNet.DE
Wed Apr 7 03:48:30 MDT 2010

On Wed, Apr 07, 2010 at 07:40:13PM +1000, tridge at wrote:
> Hi Volker,
>  > At a higher level -- it is just wrong to require a
>  > programming language that downloads with eleven (!)
>  > compressed Megabytes from to do the same job as
>  > the build system does now. Eleven Megabytes! That is just a
>  > HUGE bloat for a simple make.
> I really have to wonder if you are joking about this!
> That 11M replaces make, m4, autoconf and many other tools.

Is that also in the final tar.gz? I see a difference in
having to ship python to the end-user just to be able to
compile Samba3 to having to install python/autoconf/whatever
to create the final configure/make. And, "make" is pretty
much an already accepted requirement to build Samba3.

> That 11M (which nearly all Samba developers and users won't have to
> download at all), ends up allowing us to reduce the size of the
> compiled Samba4 from 1.1G to 110M. Now that is bloat!

I don't mind Samba4 to convert to waf.

> That 11M allows us to replace about 9k lines of pretty much
> unintelligable m4 with much more readable wscript files. It buys us a
> better build system, with better dependencies and the possibility of a
> greater degree of sharing between the s3 and s4 branches. 

How does the build system affect sharing code?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <>

More information about the samba-technical mailing list