[Scons-users] SCons as a library

[Bill Deegan]

On Wed, Oct 9, 2013 at 10:30 PM, Matias Iturburu <
matias.iturburu at tallertechnologies.com> wrote:


> On 09.10.2013 16:36, Matias Iturburu wrote:

>>>

>>>> Hello list.

>>>>

>>>> At work I'm maintaining a build tool based on SCons, fudepan-build (

>>>> https://code.google.com/p/**fudepan-build/<https://code.google.com/p/fudepan-build/>

>>>> ).

>>>> It's been used quite a lot for a number of projects and every project

>>>> in FuDePAN (http://fudepan.org.ar/).

>>>>

>>>> The tool has grown over the years and itself has its number of design

>>>> mistakes sort of defeating the purpose of using SCons.

>>>>

>>>> [...]

>>>>

>>>> Do you guys knows of something that already does that? or some other

>>>> comment about the project?

>>>>

>>>>

>>> can you possibly tell which functionality exactly is missing in SCons,

>>> and that you have to add or provide with your own fudepan-build tool? Maybe

>>> it could be added to either SCons or Parts (Did you already have a look at

>>> the latter? Visit http://parts.tigris.org/ )...just as an idea.

>>>

>>>

>> Haven't seen Parts. Really interesting.

>>

>> I think is not a matter of things that are missing in SCons as much as

>> things that SCons should not be doing, like checking out my (or my

>> organization's) project from its repo, running unittests or coverage

>> metrics against my project, running static analysis tools. Actions that

>> doesn't have to do with actually building the project but with giving new

>> members a faster ramp up and formalizing the organization workflow.

>>

>>

>>

>> Not sure why you think that SCons should not be doing those tasks.

>>

>

Any comment on this question?




> Many users have added such logic to their SCons implementation with great

>> success.

>>

>

> Can you point me to some example? You are talking about in a forks? I

> don't want to maintain my own SCons version...

>


No I am not talking about a fork.
Take a look here: http://www.scons.org/wiki/SconsRecipes#Testing
There are many examples of builders for running various tools there. None
of which require forking SCons.




>

>

>> It's likely that you just don't want SCons to do those items by default

>> (without explicitly asking for them to be run).

>>

>

> Right.

> For instance. In fudepan, fbuild keeps track of the fundation's projects,

> so any newcomer can download fbuild and say *fbuild targets* and it will

> list the projects available to him, he can then download it with *fbuild

> myproject:checkout* and run its unittests with *fbuild myproject:test* and

> so on...

>


Still not sure why you can't do this with vanilla SCons and some of your
own builders.
And perhaps a few aliases..

-Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://four.pairlist.net/pipermail/scons-users/attachments/20131010/c60999b1/attachment.html