[Libburn] structure.h

[Laurent Sansonetti]

On Wed, 2004-01-14 at 03:56, Derek Foreman wrote:
> On Tue, 13 Jan 2004, Laurent Sansonetti wrote:
> 
> > Hi guys,
> >
> > It seems that libburn.h is the only header file which is installed with
> > the library.
> >
> > Is it intentional that structure.h isn't copied as well?  This file
> > contains (imho) information such as chaining between discs, sessions and
> > tracks, which can be useful when writing some burning software.
> >
> > # This header is required by test/toc.c.
> 
> Yes, it's intentional that libburn.h is the only header, some of what's in
> structure.h will be moved to libburn.h eventually.
> 
> it's in the TODO file, actually, "make toc.c compile without any internal
> headers".  I just haven't finished it yet.
> 
> The problem is, some of the stuff in structure.h is only useful
> internally, so if I export the whole mess and allow direct access to
> those structures, if I want to add/remove a member later, I break
> applications currently linked with the lib.

Mmh I see your point.  What about creating new functions to wrap this:

struct burn_session *
burn_disc_get_sessions (struct burn_disc *disc, int *n_sessions);

struct burn_track *
burn_session_get_tracks (struct burn_disc *disc, int *n_tracks);

struct burn_toc_entry *
burn_track_get_entry (struct burn_disc *disc);

etc... ?

BTW, I tried libburn a few days ago with some friends and it seems that
it can only recognize drives with 2.6.x Linux kernel releases (do not
work with 2.4.x releases).   Is it a well known issue?

Cheers, and keep the good work!  The Ruby bindings are almost finished.

--
Laurent