> -Original Message-
> From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 14, 2002 8:15 PM
> As a generalization of this and Tom's _NAME, what about:
>
> nobase_include_HEADERS = ...
> nobase_include_HEADERS_TRANSFORM = s,^foo/bar/delta/,,
>
> This would be s
>>> "Robert" == Robert Collins <[EMAIL PROTECTED]> writes:
[...]
Robert> I fiddled around with various ideas before posting. A
Robert> different one was
Robert> nobase_include_HEADERS = ...
Robert> include_HEADERS_strip = foo/bar/delta
Robert> where foo/bar/delta is removed from the path.
> -Original Message-
> From: Tom Tromey [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 14, 2002 10:40 AM
> Rob> While defining a new target to be $(includedir)/foo lets
> you work
> Rob> around this, it would be great to do something like:
> Rob> nobase_preserve_foo_HEADERS = ...
> "Rob" == Robert Collins <[EMAIL PROTECTED]> writes:
Rob> Installation of headers in subdirectories is more complex than it
Rob> could be (IMO).
Thanks for this info.
Rob> The nobase_ prefix allows utilising an existing directory tree,
Rob> but a non-recursive build will almost always have
Just an idea.
I use automake to make non-recursive build environments fairly routinely
now. (Recursive-make-considered-bad ...)
Installation of headers in subdirectories is more complex than it could
be (IMO).
The nobase_ prefix allows utilising an existing directory tree, but a
non-recursive b
