build: separate deps for int and ext libweston users
authorPekka Paalanen <pekka.paalanen@collabora.com>
Thu, 18 Apr 2019 13:43:55 +0000 (16:43 +0300)
committerPekka Paalanen <pekka.paalanen@collabora.com>
Thu, 24 Oct 2019 10:29:33 +0000 (13:29 +0300)
commit71ff95a54496eda9ef567f1a4a3ed39936ddd129
tree719b1f1037d0908242e920f08682d7d675da99c0
parent17389d63fdcee646505a8a8545ce55b671c74128
build: separate deps for int and ext libweston users

We have two kinds of libweston users: internal and external. Weston, the
frontend, counts as an external user, and should not have access to libweston
private headers. The shell plugins are external users as well, because we
intend people to be able to write them. Renderers, backends, and some plugins
are internal users who will need access to private headers.

Create two different Meson dependency objects, one for each kind.

This makes it less likely to accidentally use a private header.

Screen-share is a Weston plugin and therefore counts as an external user, but
it needs the backend API to deliver input. Until we are comfortable exposing
public API for that purpose, let it use internal headers.

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
17 files changed:
compositor/meson.build
desktop-shell/meson.build
fullscreen-shell/meson.build
ivi-shell/meson.build
libweston-desktop/meson.build
libweston/backend-drm/meson.build
libweston/backend-fbdev/meson.build
libweston/backend-headless/meson.build
libweston/backend-rdp/meson.build
libweston/backend-wayland/meson.build
libweston/backend-x11/meson.build
libweston/meson.build
libweston/renderer-gl/meson.build
pipewire/meson.build
remoting/meson.build
tests/meson.build
xwayland/meson.build