strk wrote:
Gnash ./configure is big because we don't reuse code much.
One of the developers is working on that.
That won't help as m4 is a macro language, and will blindly just
replace everything anyway. Gnash's configure is big because we have alot
of support for obscure things to we can build on as many architectures
as possible. The size of the script isn't really that important as it
doesn't effect runtime performance.
- rob -
_______________________________________________
Gnash-dev mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnash-dev
signature.asc