[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] [PATCH] Various fixes to build for android

From: Eric S. Raymond
Subject: Re: [gpsd-dev] [PATCH] Various fixes to build for android
Date: Fri, 29 Aug 2014 14:31:08 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

Matt <address@hidden>:
> There still remains issue 3 below: there are many symbols in libgps
> which are needed by libgpsd, but libgpsd isn't linked against
> libgps.
> One consequence: if you want to dlopen() libgpsd for some reason,
> you need to dlopen() libgps first; whereas if libgpsd were linked
> against libgps, the runtime linker would load libgps automatically
> for you when you dlopen()'ed libgpsd.
> Attached is a program that does this, to show the hoops such a
> program has to jump through. I'm not claiming the program is
> inherently useful in any way at all, nor even a good idea :-)
> Why is it drastic and/or incorrect to simply link libgpsd against libgps?

I'm twitchy about this because I dimly remember trying it at one point
and having things break spectacularly on one or more of our target
platforms. But I don't remember where or why.  Groveling through the
change comments has not proved enlightening.

Now that I think about it, though, this problem might have been an artifact
of reverse linkage.  I guess it  might be time to try this again, carefully.

Alternatively, if we can identify the subset of library modules in libgps
that libgpsd uses, perhaps we can simply add them to the list libgpsd
is built from. 
                <a href="";>Eric S. Raymond</a>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]