[Scons-users] Request for comment: configuration	extension	design
    Evan Driscoll 
    driscoll at cs.wisc.edu
       
    Fri Jun 29 20:04:30 EDT 2012
    
    
  
[This message is an almalgamation of a few responses.]
On 06/29/2012 03:57 PM, William Deegan wrote:
 > Best to stick such in the wiki so others can collaborate on it.
Good idea.
I put it up at 
http://scons.org/wiki/EvanEnhancedConfigurationPackageProposal. Feel 
free to rename it and/or link it from somewhere; right now I just linked 
to it from my user page.
I'm too lazy to format the table so it's just a big <pre> block. There 
should be fewer markup languages. :-)
On 06/29/2012 04:46 AM, Pawel Tomulik wrote:
> it seems like I work partially on similar topic. I'm going to make
> scons command-line similar to make/(auto)configure GNU tools. The
> variables will be used by packaging facilities I'm currently working on.
> I also plan to make scons compatible with some external packaging
> tools, such as Debian's (debhelper and friends).
How much other overlap is there? Any? Conceivably I could just pull in 
whatever you're writing. What are the goals of the packaging facilities 
you're writing?
On 06/29/2012 11:12 AM, Damien wrote:
 > What you're describing is close to what we actually do.
I fully expect that a lot of what I have is close to what lots of people 
do; it seems to me like needing to support lots of configurations like 
that would be a common need. I'm just trying to save people writing the 
same the same thing repeatedly in slightly different ways. :-)
If there are any difficulties you ran into and such with your 
experience, it would probably help to know. Or things you wish you had 
done differently. Or on a positive note things that make you go "man I'm 
smart, I'm glad I did that" :-).
 > We don't use custom Builders, and maybe we should, I like what you
 > propose there. I like the Abstract flags proposal too.
One goal that I didn't mention is that I want to make some of the parts 
separable, e.g. you could pull in just the part that adds a bunch of env 
variables for the abstract flags. You'd just need to add something to 
either your CCOM (/CXXCOM/SHCOM/LINKCOM/...) or CCFLAGS (/CFLAGS/...).
(I'll be modifying CCOM and friends so that the developer can modify 
CCFLAGS and stuff without worrying about removing the abstract flag 
variables, but as long as you're careful there's no reason they couldn't 
go there.)
Evan
    
    
More information about the Scons-users
mailing list