Re: [Gtkpod-devel] Libgpod should return supported codecs from it's device

[<luc...@gm...>]

Hi Christophe, just wondering if you had a chance to take a look?

Thanks much

Gary

On Sun, Dec 12, 2010 at 2:47 AM, Christophe Fergeau <cfe...@gm...>wrote:

> Hi Lucas,
>
> 2010/12/8 luc...@gm... <luc...@gm...>:
> > After much examination I modified libgpod to return a GList of supported
> > codecs, read from SysInfoExtended.
>
> Thanks for the patch, I haven't had time to look at it yet though :-/
> However, the functionality it adds is useful, though I'll have to
> check with banshee and amarok people which format would work for them
> for the returned list so that we have something generic enough.
>
> >
> > Also, when I was trying to test this with Rhythmbox I ran into a serious
> > issue attempting to link the new library...  I ended up having to install
> > the new version of libgpod over top of the old version...  NOthing I did
> > would influence which libgpod version got linked too.
> >
> > I thought the variable for this sort of thing was CPPFLAGS.  Here's the
> > flags I used in rhythmbox:
> > --enable-maintainer-mode --enable-uninstalled-build 'CFLAGS=-g -O0'
> > 'CXXFLAGS=-g -O0' 'JFLAGS=-g -O0' 'FFLAGS=-g -O0' CPPFLAGS='-L
> > /usr/local/lib/ -I /usr/local/include/gpod-1.0/'
> >
>
> At compile time, you can set PKG_CONFIG_PATH to
> /usr/local/lib/pkgconfig to get rhythmbox to find the libgpod you
> compiled. However, at runtime, you also have to instruct the dynamic
> linker (the thing which loads shared libraries) that it should look in
> /usr/local/lib in addition to its default search path, otherwise it
> won't load the libgpod you compiled yourself. You can do that by
> setting LD_LIBRARY_PATH to /usr/local/lib, I think this is the step
> you were missing.
>
> Thanks for the patch, sorry for being slow in answering and looking at it,
>
> Christophe
>