[gst-devel] Re: [gst-cvs] CVS: gstreamer acinclude.m4,1.20,1.21

David I. Lehn dlehn at vt.edu
Tue Dec 11 08:30:05 CET 2001


* Thomas Vander Stichele <thomasvs at users.sourceforge.net> [20011211 10:13]:
> Modified Files:
> 	acinclude.m4 
> Log Message:
> added AM_PATH_ARTS
...
> +# Configure paths for ARTS
> +# Philip Stadermann   2001-06-21
> +# stolen from esd.m4
> +
> +dnl AM_PATH_ARTS([MINIMUM-VERSION, [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]]])
...

If you plan to continue down this path may I make a suggestion?  The way
OMS handled this was a bit cleaner IMHO.  We had a m4/ dir under the
root that we'd copy all the required m4s into.  Then in autogen.sh we'd
cat them all together.   Makes it MUCH easier to update individual
files.  Can even write a script in autogen.sh to compare dates with the
real files and warn user or copy files or whatever.

Of course, you know this is totally wrong anyway.  The whole idea is
that developers using CVS code will have all the dev packages installed
so the m4s exist already in a standard location.  When you make dist it
will create a configure file that works for people regardless of whether
they have the m4s installed or not.

I'd go with the m4/ dir thing if you think developers can't handle
installing a few -dev packages.

-dave
-- 
David I. Lehn <dlehn at vt.edu>  | http://www.lehn.org/~dlehn/
Computer Engineering Graduate @ Virginia Tech in sunny Blacksburg, VA




More information about the gstreamer-devel mailing list