Feature #56
closedProperly separate libbabeltrace and libctf
0%
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.
Updated by Yannick Brosseau almost 13 years ago
That will need to be discussed as it is not really sure that we want to expose CTF directly.
Updated by Mathieu Desnoyers almost 13 years ago
- Status changed from New to Invalid
Issues with API definition and content of libraries exposed to users is a bug, not a feature.
Updated by Anonymous almost 13 years ago
- Target version deleted (
4)
Just for the record, it's possible to change an issue from a tracker to another (like from Feature to Bug), just click the (More) link next to Change properties.