On Tue, 17 Aug 2010 17:34:28 -0400
"Alfred M. Szmidt" <[email protected]> wrote:
> > > Is that a bug or a featuer?
> >
> > Neither. It is simply that --disable-whatever is equivalent to
> > --enable-whatever=no, so that giving it an option is in fact
> > useless.
> >
> > > I cannot see why you'd want to use --disable-FOO=yes/no.... Can
> > > someone explain why that is useful?
> >
> > Given what I said above, it is not.
>
> it is useful if you can make use of it! because the configure
> --help output displays most options the --disable way,
> middle-clicking that and appending a no is faster and less work
> than writing it all manually the --enable way. it is also less
> error prone.
>
> ./configure --enable-{a,b,c} --disable-{d,e,f}
yes and no! having options the --enable way is still easier. ok, i talk
to the wrong person....
best wishes,
MeloDramus <[email protected]>
