Commits on Source (27)
-
Daniel Stone authored
We need this in coming patches. Signed-off-by: Daniel Stone <daniels@collabora.com>
2a9f7aab -
Daniel Stone authored
We have this everywhere, so we can move it out of process_info. Signed-off-by: Daniel Stone <daniels@collabora.com>
ca55f054 -
Daniel Stone authored
This is just an empty shell around weston_process. Signed-off-by: Daniel Stone <daniels@collabora.com>
d8114aa8 -
Daniel Stone authored
It's not a libweston thing, it's a part of the frontend. Signed-off-by: Daniel Stone <daniels@collabora.com>
4326d3c7 -
Daniel Stone authored
Now we only have one place we launch processes, we can just inline this wl_list_insert. Signed-off-by: Daniel Stone <daniels@collabora.com>
348465cd -
Daniel Stone authored
It's not libweston, so it shouldn't be weston_. Signed-off-by: Daniel Stone <daniels@collabora.com>
abe893d8 -
Daniel Stone authored
wet_process provides a cleanup function which can be called, but only passes the process itself. This relies on the process struct being inlined in something else meaningful, and means that we can't allocate them on demand. Add a 'data' argument which allows users to pass meaningful data to their cleanup handler. Signed-off-by: Daniel Stone <daniels@collabora.com>
c2cd15ed -
Daniel Stone authored
Don't call cleanup if we haven't been given anything to call. Signed-off-by: Daniel Stone <daniels@collabora.com>
a72d0c1b -
Daniel Stone authored
Instead of reusing an inline wet_process struct, allocate a new wet_process every time we go to launch Xwayland. Signed-off-by: Daniel Stone <daniels@collabora.com>
31dcd987 -
Daniel Stone authored
Every time we call wet_client_launch, we now allocate a new wet_process, which is always cleaned up by the compositor core and not by the users. In doing this, weston_client_launch is renamed to wet_client_launch, since wet_ is for the frontend and weston_ is for libweston. Signed-off-by: Daniel Stone <daniels@collabora.com>
9a7c88c2 -
Daniel Stone authored
Now that we have wet_process everywhere, print out the process exit status in the main handler. Signed-off-by: Daniel Stone <daniels@collabora.com>
991b3fb2 -
Daniel Stone authored
Reuse the body of the process cleanup as a separate function. Signed-off-by: Daniel Stone <daniels@collabora.com>
d5bcc260 -
Daniel Stone authored
Remove all handling of process/PID internals from libweston's Xwayland launcher, and keep this only in the frontend. libweston now only sees the wl_client and nothing else. Signed-off-by: Daniel Stone <daniels@collabora.com>
e64232a8 -
Daniel Stone authored
We rely on the Xwayland launcher setting $DISPLAY to connect to our own X server. Make very sure in the tests that we're actually getting that set properly. Signed-off-by: Daniel Stone <daniels@collabora.com>
f3608189 -
Daniel Stone authored
This shouldn't be relevant to the core. Signed-off-by: Daniel Stone <daniels@collabora.com>
104676ec -
Daniel Stone authored
compositor_destroy_listener tells us exactly what it is. Signed-off-by: Daniel Stone <daniels@collabora.com>
506901d9 -
Daniel Stone authored
Make sure that we consistently mark the client as NULL when it's destroyed, and destroy it on process exit as well, so we have a consistent state. Signed-off-by: Daniel Stone <daniels@collabora.com>
eff5e7e0 -
Daniel Stone authored
Return a void * from wet_load_xwayland, so we can later pass it back to explicitly call the cleanup. Signed-off-by: Daniel Stone <daniels@collabora.com>
10f6b99a -
Daniel Stone authored
Currently Xwayland is cleaned up by a destroy listener. The problem with this is that this is true for both libweston's Xwayland support as well as the frontend's. Add an explicit destroy step to Xwayland frontend which will cleanly destroy the process as well as any other resources. Signed-off-by: Daniel Stone <daniels@collabora.com>
388702c1 -
Daniel Stone authored
When we exit, clean up any process we launched. Signed-off-by: Daniel Stone <daniels@collabora.com>
52987b03 -
Daniel Stone authored
It does what it says on the box: is true when the compositor is in the process of shutting down. Signed-off-by: Daniel Stone <daniels@collabora.com>
579019a7 -
Daniel Stone authored
We previously had our own local variable for this, but now we can just use the one in weston_compositor. Signed-off-by: Daniel Stone <daniels@collabora.com>
9aa68248 -
Daniel Stone authored
When we're shutting down, don't try to restart the shell client. Signed-off-by: Daniel Stone <daniels@collabora.com>
570bf182 -
Daniel Stone authored
When we're shutting down, don't try to restart the IM client. Signed-off-by: Daniel Stone <daniels@collabora.com>
2896a0e9 -
Daniel Stone authored
We were freeing the writeback-format blob on error, but not on success. Signed-off-by: Daniel Stone <daniels@collabora.com>
be559097 -
Daniel Stone authored
We were leaking a couple of buffers (both input and output), and also a couple of filenames. Signed-off-by: Daniel Stone <daniels@collabora.com>
42f071e8 -
Daniel Stone authored
Now that we clean up everything to do with wet_process, we can enable memleak checking in CI. Signed-off-by: Daniel Stone <daniels@collabora.com>
7c868576