Project

General

Profile

Actions

Bug #64

closed

Properly separate libctf and libbabeltrace

Added by Mathieu Desnoyers almost 13 years ago. Updated almost 13 years ago.

Status:
Resolved
Priority:
High
Assignee:
Julien Desfossez
Category:
-
Target version:
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.


Related issues 1 (0 open1 closed)

Has duplicate Babeltrace - Feature #56: Properly separate libbabeltrace and libctfInvalid02/16/2012

Actions
Actions

Also available in: Atom PDF