v4l-utils follows the classic odd unstable / even stable release numbering,
this is the start of a new 0.9.x dev cycle leading to a 0.10.x (or maybe a
1.x) release. The plan for 0.9.x is to:
1) Keep the libv4l1 and libv4l2 ABI's compatible with 0.8.x
2) Change the libv4lconvert ABI, changing the soname to libv4lconvert.so.1
(from libv4lconvert.so.0), this is needed to be able to add plugin
support to libv4l2
3) Allow for somewhat more adventurous changes, until later in the 0.9.x
cycle, when things should stabilize again
Note WRT 2), that there is no promise of a stable libv4lconvert.so.1 ABI
until 0.10.0 is released!
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
-V4L_UTILS_VERSION=0.8.5
+V4L_UTILS_VERSION=0.9.0-test
# These ones can be overriden from the cmdline
# Note the -I../.. this assumes all sources live in a 2 level dir hierarchy!
override CPPFLAGS += -I../../include -I../../lib/include -D_GNU_SOURCE -DV4L_UTILS_VERSION='"$(V4L_UTILS_VERSION)"'
override LDFLAGS += -L../../lib/libv4l1 -L../../lib/libv4l2 -L../../lib/libv4lconvert
-# This is the soname version
-LIB_RELEASE = 0
# And last various rules
override CPPFLAGS += -fPIC
endif
+# This is the soname version
+LIB_RELEASE = 0
+
all: $(TARGETS)
-include $(V4L1_OBJS:.o=.d)
override CPPFLAGS += -fPIC
endif
+# This is the soname version
+LIB_RELEASE = 0
+
all: $(TARGETS)
-include $(V4L2_OBJS:.o=.d)
override CPPFLAGS += -DLIBDIR=\"$(LIBDIR)\" -DLIBSUBDIR=\"$(LIBSUBDIR)\"
+# This is the soname version
+LIB_RELEASE = 1
+
all: $(TARGETS)
-include $(CONVERT_OBJS:.o=.d)