[rtems-tools commit] rtems-bsp-builder: Change to waf build system

[Chris Johns]

On 15/6/21 4:28 pm, Sebastian Huber wrote:
> On 15/06/2021 07:50, Chris Johns wrote:
>> On 15/6/21 3:44 pm, Sebastian Huber wrote:
>>> On 15/06/2021 06:03, Chris Johns wrote:
>>>> On 8/6/21 10:23 pm, Sebastian Huber wrote:
>>>>> On 08/06/2021 14:08, Joel Sherrill wrote:
>>>>>> Is the kernel rsb recipe fixed yet? That was a blocker.
>>>>> Is this really a blocker? Can't this be done on demand when someone wants to
>>>>> update them?
>>>> This depends on our shared view of supporting an eco-system.
>>>>
>>>> Support was added before we moved the build system to waf to build the
>>>> kernel as
>>>> part of a vertical software stack and this I consider important.
>>> I didn't say the contrary. What I don't agree with is the work package ordering
>>> and dependency chain. The time I wasted on keeping the build system zombie more
>>> or less alive I could have spent on updating the RSB.
>> No doubt. I am responding to your comment that this task can get done on demand.
>> How does the ecosystem view of this fit into your "demand" driven view?
> 
> On demand means if someone wants update the RSB, the files are converted to the
> new build system. The files using the old build system still work since they use
> commits which have the old build system included. At least this is how I think
> the RSB works.

The ecosystem is a backwards compatible means to do something in RTEMS. Users
can depend on the interface provided to work. What and how is for us to solve as
long we maintain the interface. We are currently providing command line
interfaces and the RSB is a central part. Vertical software stacks also form an
important part for the same reasons and we should be moving to this being a way
users of releases work. As a result I see the RSB being able to build a kernel
as important to us being able to make a release. My hope is this falls under the
description of "demand".

If this is pushed through and the task it left for the "demand" queue it is
actually being placed on my queue because I am the one releasing RTEMS and I
think having these sorts of things resolved at release time is not great because
there is never enough testing.

I would rather we discuss and understand these things up front rather than later.

Chris