Re: Why so many Weston APIs were moved to libweston-internal.h

2019-08-30 Thread Pekka Paalanen
On Mon, 19 Aug 2019 11:45:38 +0300 Marius Vlad wrote: > Hi Xichen, > > The main reason for doing this move/split is because, over the years, a > lot of helper API has crawled into libweston, making it quite in large > size and hard to reason about the symbols usefulness. That header was/is > a c

Re: Why so many Weston APIs were moved to libweston-internal.h

2019-08-19 Thread Marius Vlad
Hi Xichen, The main reason for doing this move/split is because, over the years, a lot of helper API has crawled into libweston, making it quite in large size and hard to reason about the symbols usefulness. That header was/is a catch-all for ``where do I put this symbol declaration?''. The split

Why so many Weston APIs were moved to libweston-internal.h

2019-08-16 Thread Sichem Zhou
Hi weston developers, I noticed the new weston(since version 6.0.91), it introduced a new internal header `libweston-internel.h`. Many useful APIs for compositor writers were moved here. For example, personally I heavily use temporary binding thus I use `weston_binding_destroy` to remove those bi