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...
Thanks,
Karel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
