On 8/25/17, Jorge Ramirez <jorge.ramirez-or...@linaro.org> wrote: > On 08/25/2017 02:50 PM, Paul B Mahol wrote: >> On 8/25/17, Jorge Ramirez-Ortiz <jorge.ramirez-or...@linaro.org> wrote: >>> From: Alexis Ballier <aball...@gentoo.org> >>> >>> In preparation to support the integation of the V4L2 API for encoding >>> and decoding, move v4l2 related files to libavcodec. >>> >>> v4l2-common was renamed to v4l2_fmt for clarity (v4l2-common.h belongs >>> to the V4L2 API) >>> >>> Signed-off-by: Alexis Ballier <aball...@gentoo.org> >>> Reviewed-by: Jorge Ramirez-Ortiz <jorge.ramirez-or...@linaro.org> >>> --- >>> configure | 6 ++- >>> libavcodec/Makefile | 1 + >>> libavcodec/v4l2_fmt.c | 105 >>> ++++++++++++++++++++++++++++++++++++++++++++++ >>> libavcodec/v4l2_fmt.h | 57 +++++++++++++++++++++++++ >>> libavdevice/Makefile | 6 +-- >>> libavdevice/v4l2-common.c | 105 >>> ---------------------------------------------- >>> libavdevice/v4l2-common.h | 61 --------------------------- >>> libavdevice/v4l2.c | 40 ++++++++++++------ >>> libavdevice/v4l2enc.c | 12 +++++- >>> 9 files changed, 206 insertions(+), 187 deletions(-) >>> create mode 100644 libavcodec/v4l2_fmt.c >>> create mode 100644 libavcodec/v4l2_fmt.h >>> delete mode 100644 libavdevice/v4l2-common.c >>> delete mode 100644 libavdevice/v4l2-common.h >>> >> Does lavd stuff now depends on lavc? > > um yes, v4l2 in/out devices (lavd) do use a common file now present in > lavc (ie: v4l2_fmt.c). > > see libavcodec/Makefile: > > OBJS-$(CONFIG_V4L2) += v4l2_fmt.o > OBJS-$(CONFIG_V4L2_M2M) += v4l2_m2m.o v4l2_buffers.o > > also note that the common file doesn't depend on the new V4L2_M2M > decoders/encoders being available (only on V4L2)
Than relevant devices in lavd should be marked to depend on lavc. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
