Actions
Feature #56
closedProperly separate libbabeltrace and libctf
Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/16/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.
Actions