* [ltt-dev] Babeltrace API plan
@ 2011-11-04 19:45 Mathieu Desnoyers
0 siblings, 0 replies; only message in thread
From: Mathieu Desnoyers @ 2011-11-04 19:45 UTC (permalink / raw)
Hi!
After a few people asking questions about the direction I plan to take
regarding the Babeltrace Common Trace Format (CTF) reading API, I think
it's good that I clarify this publicly on the mailing list:
For those interested in using it from external applications:
a) first create your prototype by including the private babeltrace
headers you need.
b) then, as you do this, you'll find out what you need exported
c) please propose a patch to babeltrace to export what you need
through a clean API
I'm not exporting all the headers that are needed to access the
information read by babeltrace yet, because I don't want to expose the
guts of babeltrace to applications (which would be a problem if we want
to change the implementation). So we really need to come up with a clean
API to allow access to the CTF "ir" (intermediate representation) of the
trace.
Thanks,
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-11-04 19:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-04 19:45 [ltt-dev] Babeltrace API plan Mathieu Desnoyers
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox