Actions
Bug #64
closed
MD
JD
Properly separate libctf and libbabeltrace
Bug #64:
Properly separate libctf and libbabeltrace
Start date:
02/17/2012
Due date:
% Done:
0%
Estimated time:
Description
Right now, the "libbabeltrace" and "libctf" parts are one big inter-dependant blob.
Ideally we should separate both of those in distinct libraries, each with their own public API. (.h's and whatnot)
libbabeltrace will probably depend on libctf, since it uses it as IR, but the dependency would be one-way.
This would allow applications to implement CTF parsing without having to import the babeltrace-specific libraries.
Moreover, it will allow LTTngTop to use libbabeltrace, which it cannot do it its current state because of missing open with mmap support.
Actions