[vorbis-dev] Distribution Fixes

[Ali Abdin]

* Monty (xiphmont at xiph.org) wrote at 13:47 on 28/10/00:
> 
> 
> > As for the *-config scripts, I see both sides.  The typical way to
> > detect things without using autoconf (i assume this leaves you with
> > plain makefiles) is to have multiple CFLAGS lines an let the user
> > choose, or multiple build targets (not really all that great). LAME does
> > this.  I hate it :)  That's why autoconf is in such wide use in the
> > first place.
> 
> I actually opt for the Makefiles (with platform detection); although
> you need to add new entries for new platforms, you generally want to
> thoroughly test infrastructure on a new platform before releasing it
> to the world anyway.  And when one relies on a single-layer build
> mechanism, bugs in the build system itself are less likely to bite
> you.
> 
> That said, I have no real problem with automake/autoconf.  It has
> undeniable flexibility over a straight Makefile system.
> 
> The -config system is mostly wasted on Vorbis.  You don't need to know
> where the libs are and you don't need to know where the headers are.
> This is a feature, not a bug.  Ogg/Vorbis has no compile-time
> build-specific customization and it never will.  There'd be nothing to
> ask *-config except where the installation is, and there's *no reason
> to know that*.  If such things are installed and your build system
> can't find them by the standard magic, then your build system is
> *broken*, not flawed.

Fine remove them. No big loss. Really. :)

Regards,
Ali

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.