|
»
»
« Return to Thread: g_hash_table_get_keys
Re: g_hash_table_get_keys
by Michael Banck-3
::
Rate this Message:
On Sun, May 04, 2008 at 02:20:49AM +0200, Daniel Gollub wrote:
> On Sunday 04 May 2008 00:51:39 Graham Cobb wrote:
> > On Saturday 03 May 2008 15:26:43 Daniel Gollub wrote:
> > > I guess "libcheck_pic*" is Debian/Ubuntu specific?
> > > openSUSE builds libcheck with -fPIC by default. We could also hack
> > > FindChek.cmake module to look also for libcheck_pic
> > >
> > > Quick look into FindCheck.cmake turned out to make use of pkg-config. But
> > > i guess this libcheck_pic don't have a own .pc file - right?
> >
> > That is right. Maybe it should be special-cased in FindCheck.cmake: do the
> > pkgconfig lookup but then check if the file /usr/lib/libcheck_pic.a exists
> > and, if so, change the value of CHECK_LIBRARIES (issuing a warning if you
> > like, so people know why the pkgconfig data is being ignored).
>
> Is there any reason to build check not with pic? And does it makes sense at
> all to have a archive with pic? Is there in Debian/Ubuntu shared library at
> all for check?
The reason is because there is no dynamic library, Debian/Ubuntu just
ships the static libcheck.a, which is (by policy) built without -fPIC.
To cater for linking needs, an additional libcheck_pic.a is provided. I
am not sure what the reason for no dynamic library is, probably it's
either because upstream discourages it, or the API is not stable (or
nobody requested a dynamic lib yet).
The above means that on Debian/Ubuntu, the only question is about
linking the whole test-case statically, or just libcheck. In either
case, it will have to be relinked for a new version of check.
Michael
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
> On Sunday 04 May 2008 00:51:39 Graham Cobb wrote:
> > On Saturday 03 May 2008 15:26:43 Daniel Gollub wrote:
> > > I guess "libcheck_pic*" is Debian/Ubuntu specific?
> > > openSUSE builds libcheck with -fPIC by default. We could also hack
> > > FindChek.cmake module to look also for libcheck_pic
> > >
> > > Quick look into FindCheck.cmake turned out to make use of pkg-config. But
> > > i guess this libcheck_pic don't have a own .pc file - right?
> >
> > That is right. Maybe it should be special-cased in FindCheck.cmake: do the
> > pkgconfig lookup but then check if the file /usr/lib/libcheck_pic.a exists
> > and, if so, change the value of CHECK_LIBRARIES (issuing a warning if you
> > like, so people know why the pkgconfig data is being ignored).
>
> Is there any reason to build check not with pic? And does it makes sense at
> all to have a archive with pic? Is there in Debian/Ubuntu shared library at
> all for check?
The reason is because there is no dynamic library, Debian/Ubuntu just
ships the static libcheck.a, which is (by policy) built without -fPIC.
To cater for linking needs, an additional libcheck_pic.a is provided. I
am not sure what the reason for no dynamic library is, probably it's
either because upstream discourages it, or the API is not stable (or
nobody requested a dynamic lib yet).
The above means that on Debian/Ubuntu, the only question is about
linking the whole test-case statically, or just libcheck. In either
case, it will have to be relinked for a new version of check.
Michael
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
« Return to Thread: g_hash_table_get_keys
| Free Forum Powered by Nabble | Forum Help |