Change build specification files from YAML to JSON?

[Sebastian Huber]

On 26.04.23 00:37, Chris Johns wrote:
> On 26/4/2023 4:01 am, Sebastian Huber wrote:
>> On 25.04.23 13:02, Karel Gardas wrote:
>>> On 4/25/23 12:32, Sebastian Huber wrote:
>>>> On 25.04.23 12:10, Karel Gardas wrote:
>>>>> On 4/25/23 11:03, Sebastian Huber wrote:
>>>>>>
>>>>>> On 25.04.23 11:00, Karel Gardas wrote:
>>>>>>> On 4/25/23 09:35, Sebastian Huber wrote:
>>>>>>>> The change from YAML to JSON for the build specification files is just an
>>>>>>>> implementation detail of the new build system. For the users of the new
>>>>>>>> build system nothing changes.
>>>>>>> Let me ask for clarification. Does this yaml -> json transition include
>>>>>>> (or not) files in RTEMS spec directory, e.g. files here:
>>>>>>>
>>>>>>> https://git.rtems.org/rtems/tree/spec
>>>>>> It would affect all YAML files in this directory and no other files.
>>>>> Oh. Let me ask, what is your future plan with the spec files? Considering
>>>>> you would like to move them to JSON, would you also like to provide some DSL
>>>>> + compiler which would generates those? Or would you just like to keep JSON
>>>>> and have developers editing those?
>>>> I would keep the JSON and have developer editing those.
>>>>
>>>> An alternative to changing the format could be to use the CSafeLoader of the
>>>> system yaml module if it is available. It is not as fast as the JSON loader,
>>>> but acceptable (0.65s to 0.2s on my machine for loading the items).
>>> Sorry for perhaps silly question, but why do you invest that much energy in
>>> optimizing build speed -- by fraction of seconds here? I so far fail so to see
>>> driving motivation force hence my question...
>> We have a fraction of a second if we use the CSafeLoader and no item cache.
>> Currently we use the SafeLoader which results in about 5 seconds. I would like
>> to use the build system for more stuff, so this could grow to 10, 15, or more
>> seconds which then start to get annoying if you work frequently with it.
> Then please outline what all you have in mind and what the long term plan is
> then we can consider the overall direction.

We work on a prototype to build libbsd, lwip, abseil-cpp, googletest, 
jsoncpp, libsodium, nats.c, protobuf, protobuf-c, utf8_range, cfs, 
zephyr, chip vendor HALs, etc. with the RTEMS build system.

-- 
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber at embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/