mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-27 20:21:24 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/ext/wayland/Makefile.am

50 lines
1.2 KiB
Makefile
Raw Normal View History

Initial Commit: Adding Wayland Video Sink
2011-11-02 09:02:11 +00:00
plugin_LTLIBRARIES = libgstwaylandsink.la
waylandsink: Build bindings for the unstable wl_scaler spec
2014-03-11 11:05:56 +00:00
libgstwaylandsink_la_SOURCES = \
gstwaylandsink.c \
waylandsink: replace the custom buffer pool with an allocator This reduces the complexity of having a custom buffer pool, as we don't really need it. We only need the custom allocation part. And since the wl_buffer is no longer saved in a GstMeta, we can create it and add it on the buffers in the sink's render() function, which removes the reference cycle caused by the pool holding a reference to the display and also allows more generic scenarios (the allocator being used in another pool, or buffers being allocated without a pool [if anything stupid does that]). This commit also simplifies the propose_allocation() function, which doesn't really need to do all these complicated checks, since there is always a correct buffer pool available, created in set_caps(). The other side effect of this commit is that a new wl_shm_pool is now created for every GstMemory, which means that we use as much shm memory as we actually need and no more. Previously, the created wl_shm_pool would allocate space for 15 buffers, no matter if they were being used or not.
2014-06-23 13:40:02 +00:00
wlshmallocator.c \
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
wlbuffer.c \
waylandsink: Build bindings for the unstable wl_scaler spec
2014-03-11 11:05:56 +00:00
wldisplay.c \
wlwindow.c \
wlvideoformat.c \
scaler-protocol.c
Initial Commit: Adding Wayland Video Sink
2011-11-02 09:02:11 +00:00
libgstwaylandsink_la_CFLAGS = $(GST_CFLAGS) $(GST_PLUGINS_BASE_CFLAGS) \
waylandsink: implement with stubs the GstWaylandVideo & GstVideoOverlay interfaces
2014-02-14 15:08:56 +00:00
$(WAYLAND_CFLAGS) $(GST_PLUGINS_BAD_CFLAGS)
libgstwaylandsink_la_LIBADD = \
$(GST_PLUGINS_BASE_LIBS) \
-lgstvideo-$(GST_API_VERSION) \
waylandsink: replace the custom GstWlShmMemory with GstFdMemory
2015-08-29 20:29:17 +00:00
-lgstallocators-$(GST_API_VERSION) \
waylandsink: implement with stubs the GstWaylandVideo & GstVideoOverlay interfaces
2014-02-14 15:08:56 +00:00
$(WAYLAND_LIBS) \
$(top_builddir)/gst-libs/gst/wayland/libgstwayland-$(GST_API_VERSION).la
Initial Commit: Adding Wayland Video Sink
2011-11-02 09:02:11 +00:00
libgstwaylandsink_la_LDFLAGS = $(GST_PLUGIN_LDFLAGS)
gst: Add better support for static plugins
2012-10-24 10:16:39 +00:00
libgstwaylandsink_la_LIBTOOLFLAGS = $(GST_PLUGIN_LIBTOOLFLAGS)
Initial Commit: Adding Wayland Video Sink
2011-11-02 09:02:11 +00:00
waylandsink: Build bindings for the unstable wl_scaler spec
2014-03-11 11:05:56 +00:00
noinst_HEADERS = \
gstwaylandsink.h \
waylandsink: replace the custom buffer pool with an allocator This reduces the complexity of having a custom buffer pool, as we don't really need it. We only need the custom allocation part. And since the wl_buffer is no longer saved in a GstMeta, we can create it and add it on the buffers in the sink's render() function, which removes the reference cycle caused by the pool holding a reference to the display and also allows more generic scenarios (the allocator being used in another pool, or buffers being allocated without a pool [if anything stupid does that]). This commit also simplifies the propose_allocation() function, which doesn't really need to do all these complicated checks, since there is always a correct buffer pool available, created in set_caps(). The other side effect of this commit is that a new wl_shm_pool is now created for every GstMemory, which means that we use as much shm memory as we actually need and no more. Previously, the created wl_shm_pool would allocate space for 15 buffers, no matter if they were being used or not.
2014-06-23 13:40:02 +00:00
wlshmallocator.h \
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
wlbuffer.h \
waylandsink: Build bindings for the unstable wl_scaler spec
2014-03-11 11:05:56 +00:00
wldisplay.h \
wlwindow.h \
wlvideoformat.h \
scaler-client-protocol.h
EXTRA_DIST = scaler.xml
CLEANFILES = scaler-protocol.c scaler-client-protocol.h
%-protocol.c : %.xml
$(wayland_scanner) code < $< > $@
%-client-protocol.h : %.xml
$(wayland_scanner) client-header < $< > $@
waylandsink/Makefile.am: Fix scaler-client-protocol.h generation
2014-05-20 16:03:39 +00:00
gstwaylandsink.c: scaler-client-protocol.h
waylandsink: replace the custom buffer pool with an allocator This reduces the complexity of having a custom buffer pool, as we don't really need it. We only need the custom allocation part. And since the wl_buffer is no longer saved in a GstMeta, we can create it and add it on the buffers in the sink's render() function, which removes the reference cycle caused by the pool holding a reference to the display and also allows more generic scenarios (the allocator being used in another pool, or buffers being allocated without a pool [if anything stupid does that]). This commit also simplifies the propose_allocation() function, which doesn't really need to do all these complicated checks, since there is always a correct buffer pool available, created in set_caps(). The other side effect of this commit is that a new wl_shm_pool is now created for every GstMemory, which means that we use as much shm memory as we actually need and no more. Previously, the created wl_shm_pool would allocate space for 15 buffers, no matter if they were being used or not.
2014-06-23 13:40:02 +00:00
wlshmallocator.c: scaler-client-protocol.h
waylandsink/Makefile.am: Fix scaler-client-protocol.h generation
2014-05-20 16:03:39 +00:00
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
wlbuffer.c: scaler-client-protocol.h
waylandsink/Makefile.am: Fix scaler-client-protocol.h generation
2014-05-20 16:03:39 +00:00
wldisplay.c: scaler-client-protocol.h
wlwindow.c: scaler-client-protocol.h
Reference in a new issue Copy permalink