[Scons-users] SCons popularity

[William Blevins]

Jason,

I know that integrating Parts into SCons is planned (eventually).  As far
trying to make an actual plan, do you think it can be integrated in
sections or will it need to be wholesale.  I haven't looked at the code.

V/R,
William

On Mon, Jun 15, 2015 at 10:25 AM, Kenny, Jason L <jason.l.kenny at intel.com>
wrote:

> Hi,
>
> Just to clarify and add to Vasily comments ( Thank you Vasily). SCons
> provides the base building block for pretty much what you need. Parts adds
> a component model and a structure to help make it easier to do stuff. Parts
> provides a structure for how certain thing are done, so different
> components can work together better. This is differs from a "raw" scons
> build in which you can do whatever you want and because of that different
> Sconstruct may not work the same or well with each other. This is really no
> different than what can happen in Make. In Parts you define a SConstruct
> which defines the set of things you want to build. In many ways you can
> view it as the "Product" and the Parts calls are the components that make
> up the product. Parts adds some dependency management between components (
> such as Parts A depends on Parts B version x.y.z) and allow for items such
> as the .a file name and path to be implicitly passed to avoid the user
> having to update many different build files with an updated so or .a lib
> file name. Parts also provides a common command like target structure to
> make it easier to control which component(s) are built. Parts does more
> than this, and does it by extending SCons vs replacing it. I know from
> certain people at work there are a few items Parts needs to improve on to
> help more with clusters, and these changes will come as resource to fix
> them become a available. Still everything in Parts is override-able on the
> command line, a config file ( needs more work however for certain cases),
> and the environment via a variable SCons supports.
>
> The current working drop of this as at http://parts.tigris.org/
> However this code is being moved to https://bitbucket.org/sconsparts
> While the code here is here is the latest is greatest ( however it might
> not be 100% stable). The work to clean up the new area is not finished yet.
> But feel free to add issues or questions on the site.
>
>
> Jason
>
>
> -----Original Message-----
> From: Scons-users [mailto:scons-users-bounces at scons.org] On Behalf Of Ray
> Sheppard
> Sent: Saturday, June 13, 2015 4:15 PM
> To: just.one.man at yandex.ru; SCons users mailing list; Paweł Tomulik
> Subject: Re: [Scons-users] SCons popularity
>
> Hi All,
>    For what it is worth, without this functionality, use of SCons on
> supercomputers is problematic.
>            Ray
>
> On 6/13/2015 10:44 AM, Vasily wrote:
> >
> > Yes, I was talking about those. I believe you can override their
> > default values by passing them as arguments, like $ scons all
> > INSTALL_ROOT=some-path
> >
> > That would need some testing, though - I did not try setting it to a
> > directory *not* under SConstruct's directory.
> >
> > Thanks,
> > Vasily
> >
> >
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20150615/46994814/attachment.html>