On Sat, Nov 10, 2012 at 03:34:22PM +0000, Måns Rullgård wrote: > Diego Biurrun <[email protected]> writes: > > On Sat, Nov 10, 2012 at 03:05:08PM +0000, Måns Rullgård wrote: > >> Diego Biurrun <[email protected]> writes: > >> > This better describes what the option actually does. > >> > --- a/configure > >> > +++ b/configure > >> > @@ -130,7 +130,7 @@ Component options: > >> > > >> > Individual component options: > >> > - --disable-everything disable all components listed below > >> > + --disable-components disable all components listed below > >> > --disable-encoder=NAME disable encoder NAME > >> > --enable-encoder=NAME enable encoder NAME > >> > --disable-encoders disable all encoders > >> > @@ -1946,7 +1946,7 @@ for opt do > >> > - --disable-everything) > >> > + --disable-components) > >> > map 'eval unset \${$(toupper ${v%s})_LIST}' $COMPONENT_LIST > >> > ;; > >> > >> I don't think this name is particularly accurate either. > > > > Suggestions? "components" is how we refer to individual muxers, decoders > > and whatnot in the code, at least in the build system, when we need an > > umbrella term. > > "Component" could mean just about anything. What you choose to call by > that name is far from obvious to a casual user.
A term that covers encoders, decoders, hwaccels, muxers, demuxers, parsers, bsfs, protocols, indevs, outdevs, devices and filters will by necessity end up being generic and only have meaning in context. That context is what we define it to mean by fiat. Experts will know it, casual users will have to look it up; but that configure option is an advanced one anyway. It is only used by people that want to build a very custom version of Libav. Such an endeavour requires becoming familiar with the details of Libav and parts of its build system. So, again, do you have an alternative to "component"? This is our best candidate ATM and not an unreasonable one IMO. The only other thing that came to my mind is "subcomponents"... Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
