--enable-feature and configuration failures

[Xabier Rodríguez Calvar]

	Hi,

I noticed and am not the only one probably that if you try to enable
some module with --enable-whatever and for that to be built,
libwhatever (or other dependencies) is needed and libwhatever is not
present, the only "warning" that you get is if you checked the list of
modules that are going to be built.

Is this intentional?

IMHO, a better behavior would be:

--disable-feature: it disables the feature even if the dependencies are
present (quite logical)
nothing: if the default is true, it checks for the dependencies and if
they are present the module is built (logical too)
--enable-feature: the user has explicitly requested to build this
module, if the dependencies are present, everybody is happy. If the
dependencies are not present, the configuration should fail and report
that some dependencies are missing, cause the user explicitle requested
that module.

Wdyt?

Best regards.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160622/aa88eee6/attachment.sig>