[PATCH weston 0/6] Rework libweston versioning, take 2(?)

[Quentin Glidic]

On 04/07/2016 16:23, Emil Velikov wrote:
> Hi all,
>
> Here is a respin of the earlier series which changes how libweston is
> named, and thus shipped. I believe all the logic/reasoning is explicitly
> stated, although if something feels amiss, please let me know.
>
> NOTE: WARNING: The series exposes a fatal bug in weston thus the tests
> fail to build (let alone run).
> Namely: atm some/many of the modules are built with unresolved symbols.
> Is that a bug or by design ? From a quick look it seems to be the
> latter.
>
> If anyone is interested in resolving this please grep through mesa for
> "no-undefined" - it handles both -no-undefined and -Wl,--no-undefined in
> a portable manner.

You cannot really fix all of them.
We should link all modules to libweston, but for weston-specific 
modules, using weston-specific functions, they will always be unresolved 
at build-time.

Cheers,

-- 

Quentin “Sardem FF7” Glidic