In which we establish a relationship between the subscriber and the scope. Once the subscriber has been created there needs to be a subscription process Implicitly using wayland protocol specifics. Protocol is a bit special in this regard as the destroying part is handled Subscriber types above have their destroy counter-parts. Like log scopes, the subscribers are also manged explicitly and both of the Users wanting to defineĪ new data stream should extend this weston_log_subscriber.įor example libweston make uses of several type of subscribers, specific to theĪ ‘logger’ type created by weston_log_subscriber_create_log()Ī ‘flight-recoder’ type created by weston_log_subscriber_destroy_flight_rec()įor the ‘weston-debug’ protocol, which is private/hidden created whenever a The subscriber object can define its own methods. Object (private) and allows customization of the back-end side of libweston. Modifications and might not represent a current list on which one shouldīesides creating a creating a scope, a subscriber ( weston_log_subscriber) Weston_log(), all the others scopes listed above could suffer various Xwayland, printing some X11 protocol actions.Ĭontent-protection-debug - scope for debugging HDCP issues.īesides ‘log’ scope, which is a generic scope, intended for usage through Xwm-wm-x11 - a scope for the X11 window manager in Weston for supporting It incorporates the scene-graph scope as well. Plane properties like CRTC_ID, FB_ID, FORMAT when doing a commit or a Weston is using for rendering the scene-graph, describes the current hardware Plane or to a renderer, current assignments of views, the compositing mode The transitions of a view as it takes before being assigned to a hardware Window), their surfaces, sub-surfaces, buffer type and format, both inĭrm-backend - Weston uses DRM (Direct Rendering Manager) as one of itsīackends and this debug scope display information related to that: details Graph comprising of layers (containers of views), views (which represent a Scene-graph - an one-shot debug scope which describes the current scene Similar to WAYLAND_DEBUG=server environmental variable but has the ability to Proto - debug scope that displays the protocol communication. Log - a debug scope for generic logging, upon which weston_log() Weston has a few scopes worth mentioning: Log scopes are managed explicitly, and destroying the scope is done using Important for the subscription part, detailed bit later. Weston_log_context is done using the scope name. You can customize the scopeīehaviour and you’ll require at least a name and a description for the scope.Ī scope name identifies that scope. Log scopes Ī scope represents a source for a data stream (i.e., a producer). Weston_log_ctx_destroy() or weston_log_ctx_compositor_destroy(). Weston_log_ctx_create() and clean-up/destroy with Instantiation of the weston_log_context object takes place using Take place much earlier without the need of a compositor instance. Instance can be brought up much more later, but in the same time logging can Weston_log_context object and is entirely separated from the mainĬompositor instance ( weston_compositor). Management of the logging framework in weston happens under the ![]() ![]() The logging framework which is (mostly) comprised of Log scopes (produces Logging in weston takes place through weston_log() function, whichĬalls a log handler ( log_handler) that has to be installed beforeĪctually calling weston_log().
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |