On Sunday 28 January 2007, Matthias Kretz wrote:
> On Sunday 28 January 2007 11:25, Tim Beaulen wrote:
> > Disable JuK from compiling, it conflicts with TagLib
>
> You mean that both taglib and JuK have an include called tag.h? Even
> though juk uses #include it picks up the one from juk and not
>
On Sunday 28 January 2007 12:24, Matthias Kretz wrote:
> On Sunday 28 January 2007 11:25, Tim Beaulen wrote:
> > Disable JuK from compiling, it conflicts with TagLib
>
> You mean that both taglib and JuK have an include called tag.h? Even though
> juk uses #include it picks up the one from juk and
Am Sonntag, 28. Januar 2007 schrieb Matthias Kretz:
> On Sunday 28 January 2007 11:25, Tim Beaulen wrote:
> > Disable JuK from compiling, it conflicts with TagLib
>
> You mean that both taglib and JuK have an include called tag.h? Even though
> juk uses #include it picks up the one from juk and no
On Sunday 28 January 2007 11:25, Tim Beaulen wrote:
> Disable JuK from compiling, it conflicts with TagLib
You mean that both taglib and JuK have an include called tag.h? Even though
juk uses #include it picks up the one from juk and not the one from
taglib (you'd expect that if it were using #