In gst-plugins.eclass we have: > my_gst_plugins="... gst_v4l gst_v4l2 ..." ... > GST_PLUGINS_BUILD=${PN/gst-plugins-/} ... > for plugin in ${my_gst_plugins}; do > gst_conf="${gst_conf} --disable-${plugin} " > done > for plugin in ${GST_PLUGINS_BUILD}; do > gst_conf="${gst_conf} --enable-${plugin} " > done so looking at gst-plugins-v4l2-0.8.12 log there is: > ./configure ... --disable-gst_v4l2 ... --enable-v4l2 and no v4l2src plugin built, while I suppose we actually wanted it?
Could you be a bit more verbose about what happens and what you think is wrong? Your problem is stated like a puzzle.
(In reply to comment #1) > Could you be a bit more verbose about what happens and what you think is wrong? > > Your problem is stated like a puzzle. > I want v4l2src plugin, i thought i can get with gst-plugins-v4l2. In eclass ${my_gst_plugins} used for disabling plugins lists options as they are in gst-plugins configure script, while ${GST_PLUGINS_BUILD} used for enabling needed plugins gets names from ebuild name. The problem seems to come when first one doesn't match the latter. I.e for gst-plugins-v4l2, ${my_gst_plugins} is 'gst_v4l2' and ${GST_PLUGINS_BUILD} is 'vl2', so eclass passes '--disable-gst_v4l2 --enable-v4l2'. Desired line would look like '--enable-gst_v4l2'.
Hmmm? What's up here, sounds like a trivial fix?
*** This bug has been marked as a duplicate of bug 190800 ***