[PATCH wayland v2 3/4] wayland-util: build/ship as separate shared library

[Pekka Paalanen]

On Tue, 4 Apr 2017 11:11:32 +0100
Emil Velikov <emil.l.velikov at gmail.com> wrote:

> On 4 April 2017 at 09:08, Pekka Paalanen <ppaalanen at gmail.com> wrote:
> > On Mon, 3 Apr 2017 19:31:50 +0100
> > Emil Velikov <emil.l.velikov at gmail.com> wrote:
> >  
> >> On 21 March 2017 at 10:05, Pekka Paalanen <ppaalanen at gmail.com> wrote:  
> >> > On Mon, 20 Mar 2017 18:21:53 +0000
> >> > Emil Velikov <emil.l.velikov at gmail.com> wrote:
> >> >  
> >> >> On 17 March 2017 at 13:32, Pekka Paalanen <ppaalanen at gmail.com> wrote:  
> >  
> >> Summarising the points below. Highlighting the key words - hope it
> >> provides some clarity.
> >>
> >> If we don't bump the version-info:  
> This line should not be here.
> 
> >> A) w/o NEEDED, aka Requires.private: libwayland-util
> >>  - Existing binaries _will_ work, as the symbols will be _implicitly_
> >> resolved at _runtime_.
> >>  - Newly build binaries _may_ (depending on a few factors) fail at _link_ time  
> >
> > Hi,
> >
> > the latter item in case A is what I do not understand. To me it seemed
> > like you were claiming that it does work, now you say it might not. Can
> > you explain, please? (*)
> >  
> The key is word here is "runtime" vs "link time".
> For A runtime will be fine, while link may not work.

How are link time and runtime different in symbol resolution?


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20170404/56ff3b66/attachment.sig>