Reduce build systems in master

Andrew Bartlett abartlet at
Tue Sep 27 23:49:56 MDT 2011

On Mon, 2011-09-12 at 19:43 +1000, Andrew Bartlett wrote:
> On Thu, 2011-09-08 at 12:00 +1000, Andrew Bartlett wrote:
> > On Thu, 2011-09-01 at 15:13 +1000, Andrew Bartlett wrote:
> > > Following up from my mail last month, attached is my proposal to reduce
> > > the build systems we need to maintain to two, the top level waf build
> > > and the autoconf build.
> > > 
> > > The s3-waf build has been incredibly important in getting us this far,
> > > but I don't we should continue to maintain three build systems now that
> > > the top level build provides all the functionality we need.
> > 
> > Günther,
> > 
> > I've not heard from you either way on this, and that worries me.  I do
> > hope I've not offended you with this work.  
> > 
> > This isn't urgent, but I've been sitting on the idea for the seven weeks
> > since I started this thread, so I would appreciate resolving it one way
> > or the other.
> > 
> > Attached is the current patch set.  Because we can now rely on the
> > source3 wscript files being called from a top level script, it removes a
> > good chunk of code, and a lot of special cases between the two build
> > systems. 
> > 
> > Please let me know how you feel about this,
> Just as a heads-up as to my plans, what I'm thinking is that if I am
> able to get this into the tree, that I'll then be able to focus on
> having one cohesive set of configure options, generated at the top level
> rather than both in wscript and source3/wscript.
> For example in an area I've been looking into, there are three
> overlapping checks for iconv. 
> Also, I would like to remove the distinction between the two methods for
> module loading, and while I can import both into a top level file, it
> seems silly for one build system to have two distinct types of modules.
> Naturally the autoconf build would still need to be accommodated, but
> this illustrates the kind of work I would like to take on, if we agree
> to move to just two build systems.
> If you or anyone else on the team has thoughts on this, could you please
> let me know, as I would like to understand if this is an area I can work
> on.


I know you are busy, so I've just left this hanging while we were busy
at SDC.  If you can let me know any objections soon, as otherwise I
would like to proceed with the patches as indicated, to ease the
preparation for a Samba 4.0 release.


Andrew Bartlett                      
Authentication Developer, Samba Team 

More information about the samba-technical mailing list