Robert Boehne <[EMAIL PROTECTED]> writes:
> I have a massive set of C++ libraries that use
> CVS libtool, autoconf and automake to build and install.
> Since users then need to have _all_ the header files
> they also need to have the configure generated config.h
>
> What is the "best" way to coer
Alex Hornby <[EMAIL PROTECTED]> writes:
>
> # Makefile.am fragment
> FOO = foo bar
> BAR = ${FOO:%=%.c}
> ...
>
> What do people think?
It'd be nice to be able to embed little fragments of perl to do things
like that, for the "static" case that is. But perhaps that idea has
come up before. Or
On Oct 28, 2000, Alex Hornby <[EMAIL PROTECTED]> wrote:
> What is the policy regarding changes to non-portable behavour?
automake is supposed to generate portable Makefiles, so I think the
default should be static expansion.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~ol
