On Mon, 2007-08-06 at 21:31 +0200, Kurt Roeckx wrote:
On Mon, Aug 06, 2007 at 04:07:51PM +0100, Sam Clegg wrote:
Looks to me like this is an opaque data type. Its only ever referenced
as a pointer type so the user of the API never needs to know what the
layout of the type really is.
So
Package: libid3tag0-dev
Version: 0.15.1b-10
Severity: normal
See subject
libid3tag0-dev: header file /usr/include/id3tag.h does not contain definition
for struct id3_file altough it references it
[EMAIL PROTECTED]:~/Personal/src/acpitail$ grep id3_file /usr/include/id3tag.h
| grep -v ^enum
On Mon, 2007-08-06 at 15:07 +0200, Folkert van Heusden wrote:
Package: libid3tag0-dev
Version: 0.15.1b-10
Severity: normal
See subject
libid3tag0-dev: header file /usr/include/id3tag.h does not contain
definition for struct id3_file altough it references it
[EMAIL
See subject
libid3tag0-dev: header file /usr/include/id3tag.h does not contain
definition for struct id3_file altough it references it
[EMAIL PROTECTED]:~/Personal/src/acpitail$ grep id3_file
/usr/include/id3tag.h | grep -v ^enum id3_file_mode
struct id3_file *id3_file_open(char
On Mon, Aug 06, 2007 at 05:20:37PM +0200, Folkert van Heusden wrote:
Looks to me like this is an opaque data type. Its only ever referenced
as a pointer type so the user of the API never needs to know what the
layout of the type really is.
Hmmm, I could do (tested and it compiles):
On Mon, Aug 06, 2007 at 04:07:51PM +0100, Sam Clegg wrote:
Looks to me like this is an opaque data type. Its only ever referenced
as a pointer type so the user of the API never needs to know what the
layout of the type really is.
So just add a struct id3_file; at the top of the file
6 matches
Mail list logo
