[MPlayer-dev-eng] configure force enable all

[Reimar Döffinger]

Hi,
On Thu, Jul 28, 2005 at 01:13:09AM +0300, Ivan Kalvachev wrote:
> The current configure uses the following meaning for --enable--foo:
> If option is autodetected by default, --enable will force it.
> if option is disable by default, --enable will autodetect it.

This is news to me. AFAIK it will force it as well. If it isn't
auto-detected by default that should be because there is no reliable
autodetection...

> Of course if somebody wants to build an minimum featued mplayer (free
> of bloat;), he have to use multiple --disable-foo options. With adding
> new options this list grows.

Well, for those who build themselves they can usually solve it by not
installing all development packages/libs. Also for a really minimum
you'd also have to go through all those libavcodec codecs *g*
But I admit it might be useful to have some kind of "minimal preset".

> I have created 2 new options --disable-all and --enable-all. The first
> one disables all optional features. The second one enables
> autodetection for all usually disable options.

I think most of these have no autodetection, so I doubt this will work.
And if they have a useful autodetection I think they should probably be
set to auto by default.

> The only exeption is --enable-bigendian, that i removed and instead
> made --force-bigendian and --force-littleendian. Anyway I believe that
> this should go in the first pass options after --target and --host-cc
> options.
> 
> I haven't changed the mmx/altvect flags (yet).

There might be a lot more like this...

> What is to be done in order the patch to be finished: 
> Of course following all options and make sure that detections are
> following the new standart. Currently there are functions that
> autodetect on " !=no". There are probably also options that doesn't
> change 'auto' to 'yes' if no autodetection is available. Also

Ah, I guess that is what I meant above.

> --enable-all is not tested if it includes stuff that shouldn't be
> included (e.g. suboptions, interdependable options etc...).
> But there are no fatal problems.

Depends on your definition of "fatal"... That's probably the most
complicated part of the patch *g*

Greetings,
Reimar Döffinger