Project

General

Profile

Actions
Copy link

Feature #56

closed

Properly separate libbabeltrace and libctf

Added by Anonymous about 12 years ago. Updated about 12 years ago.

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.

Related issues 1 (0 open — 1 closed)

Is duplicate of Babeltrace - Bug #64: Properly separate libctf and libbabeltraceResolvedJulien Desfossez02/17/2012

Actions
Actions
Copy link
 #1

Updated by Yannick Brosseau about 12 years ago

That will need to be discussed as it is not really sure that we want to expose CTF directly.

Actions
Copy link
 #2

Updated by Mathieu Desnoyers about 12 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.

Actions
Copy link
 #3

Updated by Anonymous about 12 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.

Actions
Copy link

Also available in: Atom PDF