[Python-ideas] Rewriting the build system (part 2)

[anatoly techtonik]

On Tue, Mar 17, 2015 at 8:01 PM, Ryan Gonzalez <rymg19 at gmail.com> wrote:
> On Mon, Mar 16, 2015 at 9:27 PM, Stephen J. Turnbull <stephen at xemacs.org>
> wrote:
>>
>> Ryan Gonzalez writes:
>>
>>  > I have used fbuild a LOT
>>
>> Actually, I suspect that in the relevant sense, you haven't used it a
>> lot.  Have you used it for a single program on
>>
>> 1.  more than 3 CPUs, AND
>> 2.  on each CPU, more than one (and preferably more than two) OSes, AND
>> 3.  for each CPU-OS combination, more than two different configurations
>>     of the program being built, AND
>> 4.  for each CPU-OS-configuration combination, at least 3 versions of
>>     the program source (preferably spanning a major version bump)?
>>
>
> No...but I know that Felix uses it for iPhone, OSX, Linux, ... with
> separation of host and target and multiple configurations.

What or who is Felix?

> This is also SCons. Everybody loved it until they had to maintain it. :)

I know a blind girl, who made a voice synthesizer, which works on
Windows, Linux and Android, and she used SCons to build it. That
gave me another reason to stick with this build system and try to
enhance it.

> SCons is very annoying. CMake is weird and only really useful for those
> huge, 20,000 file C++ projects.

For me the advantage of SCons is that I already know its codebase.
There a lot of room for improvement if you can tag yourself as a Python
hacker it addition to inherent potential user property.

In any, I'd appreciate the feedback on most annoying SCons feature,
because it will give a criteria for comparing it with others and for future
development.
-- 
anatoly t.