Re: Re: [scons-devel] auto-configuration plans

David Snopek wrote:
> 
> Like I said many times before, the most we can hope to share is a battery
> of configure tests.  These are just python functions that expect to have
> access to a specific API given to them as a "context" object.  Under

that sounds possible. The tests "just" need to know, which tool to use
(e.g. gcc or g++), which Libs to link to the try-compilation, which
headers to include.

This context, as you call it, has to be updated by the checks.

if you take a look at my class FeatureTest, then you see
right now, this are the member varibles:
self.ConfDefFile = ConfDefs()
self.features = {}
self.Libs = []

one could put this in a thinner wrapper object - is that what David
calls the context?

Bram, what do you think about this?

> A-A-P, this context object would be connected to the A-A-P build system. 
> If you insist on comming up with a "standalone" implementation that would
> be a third, totally different thing.

I dont see, why a standalone system should be far away. Of course it has
to parse the test configuration (which tests to run, what to expect),
but that seems to be the largest outstanding thing for a standalone
tool.

 From the useres point of view it would be _very_ nice to learn only
one syntax to specify tests.

     Joerg



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01