[Scons-users] Provide default Import to SConscript

[Jason Kenny]

>> I want a single super repo for
>> everything a project requires, as compared to be able to build
>> independent small things and then stitch them together.


I think that is not Parts... Parts is about building everything you need in one place.. given that be using the a large repo with everything in it or having Part grab data from different areas. Parts is about making it easy to manage a build with lots of components. Projects I had at Intel had 1200+ component in it. it would build all of this as a massive unified build. I recall the output being over 50GB ( object files and debug info ) The point for Parts is that component A make some output file called joe.so and otehr components need it. Parts pass this around. So cross-building is easy and if joe becomes josh.so there is one change in one file and everything works. The current SCons/Make way is to have to change this value in every place that uses component A. I should also point out the idea of a Part is to help manage the large chaos of large projects, it also adds other stuff so one should be able to use standard SCons stuff and get improved toolchain logic etc. That is the intent, however everyone I talk to rather componentize/project the build to make it more flexible. Still, Parts might not be useful for you.
________________________________
From: Scons-users <scons-users-bounces at scons.org> on behalf of Hua Yanghao <huayanghao at gmail.com>
Sent: Wednesday, February 21, 2018 1:59 PM
To: SCons users mailing list
Subject: Re: [Scons-users] Provide default Import to SConscript

Hi Bill,

> SCons is meant to be a python based make replacement.

This is actually very much not true. Make is really just dispatching
commands/keeping track of dependencies and timestamps ... it does not
provide any Scons Tools libraries etc. In my view somehow scons is
stuck in the middle of "Make" and a comprehensive build framework like
"Kbuild", more accurate, yet more difficult compared to pure Make for
small things, and yet again more difficult compared to full-fledged
build system due to the lack of a common build framework.

> What your suggesting is probably more along the lines of Parts? (Jason)
> (Which is build on top of SCons).

I think I saw parts project quite some time ago on company intranet
... , but wasn't really what I wanted. I want a single super repo for
everything a project requires, as compared to be able to build
independent small things and then stitch them together. Kbuild is
really what I wanted, kbuild would be perfect if it is build on top of
python instead of those eye-hurting shell script ... so  I setup and
build a extremely similar (even better in many ways such as
inter-configuration dependencies) thing in python/scons (only took a
few days for the very first working version).

> So if I understand properly, you want to add an alternative version of
> SConscript where the files would be presented and entirely different set of
> globals to work with?

Yes, exactly. to bring SConscript from stone-age to industrial-age,
and yet still allow you to use chisel if you insist ... :)

Best Regards,
Yangao
_______________________________________________
Scons-users mailing list
Scons-users at scons.org
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpairlist4.pair.net%2Fmailman%2Flistinfo%2Fscons-users&data=02%7C01%7C%7C4221195991d54c2aa8d508d5796596ee%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636548399584504474&sdata=kMsEVrlAi7rop6GsdvJgozDz4QErfXqq3W7wtAZifiI%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20180221/f3cf836e/attachment-0001.html>