diff options
author | Marius Vlad <marius.vlad@collabora.com> | 2019-06-24 12:00:47 +0300 |
---|---|---|
committer | Marius Vlad <marius.vlad@collabora.com> | 2019-07-18 13:34:04 +0300 |
commit | 284d5345ad38dfd0e4ee08d3da75ace0a512a2c4 (patch) | |
tree | c7aeade362ffb28fff191976614e4049f51fdefb /doc | |
parent | f387f8409aa5fcc1ba7881143bfe15b912f9323f (diff) | |
download | weston-284d5345ad38dfd0e4ee08d3da75ace0a512a2c4.tar.gz |
compositor: Destroy the compositor before the log scope
Destroying the compositor after destroying the log scope will not print
out the messages in the tear down/clean-up phase of the compositor, so
add a new tear_down function which allows keeping a valid reference to
the compositor. This way we can destroy the compositor before destroying
the scope and keep the debug messages.
While at it remove the log context destroy part from the clean-up
of the compositor and make it stand on its own.
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/sphinx/toc/libweston/compositor.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/sphinx/toc/libweston/compositor.rst b/doc/sphinx/toc/libweston/compositor.rst index 826b5620..4fc1f57d 100644 --- a/doc/sphinx/toc/libweston/compositor.rst +++ b/doc/sphinx/toc/libweston/compositor.rst @@ -3,8 +3,9 @@ Compositor :type:`weston_compositor` represents the core object of the library, which aggregates all the other objects and maintains their state. You can create it -using :func:`weston_compositor_create`, while for destroying it and releasing all -the resources associated with it, you should use :func:`weston_compositor_destroy`. +using :func:`weston_compositor_create`, while for releasing all the resources +associated with it, you should use :func:`weston_compositor_tear_down`, +followed by :func:`weston_compositor_destroy` to destroy it. Compositor API -------------- |