Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
* [lttng-dev] [barectf] why YAML instead of CTF?
@ 2023-08-05 18:24 strager via lttng-dev
  0 siblings, 0 replies; only message in thread
From: strager via lttng-dev @ 2023-08-05 18:24 UTC (permalink / raw)
  To: lttng-dev

I have a CTF metadata file (schema) and hand-written parsers and writers for streams with that schema. I am interested in writing a tool which generates the parsers and writers (instead of hand-writing them).

It looks like barectf is similar to the tool I want to build. However, barectf reads a custom file format for the schema instead of reading a CTF metadata file.

Question: Why does barectf read a custom YAML format instead of reading CTF metadata? My plan was for my tool to read the schema from a CTF metadata file. Are there technical reasons why it's bad to make a code generator with CTF metadata as input? Because babeltrace2 can read CTF metadata files, I thought CTF metadata was machine-readable.

Thanks,
strager

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-08-07 15:14 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-05 18:24 [lttng-dev] [barectf] why YAML instead of CTF? strager via lttng-dev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox