On Tue, 2003-12-09 at 14:32, dc wrote:
AFAIK There's a third possibility : you could setup a dist-hook target
in Makefile.am which allows you to specify completely your dist rule (I
had the same problem than yours and used this method). Unfortunately, it
also means that you might have to
i see from the previous post that you use a manual VPATH methodology.
there are two approaches you can try:
1/ undo the unorthodoxy (move auto* files to top-level dir)
2/ prefix relative paths (such as ../../) w/ $(srcdir)
probably 1/ is the best for minimizing gray hairs long term, although it
Thanks for the response!
On Tue, 2003-12-09 at 08:05, Thien-Thi Nguyen wrote:
i see from the previous post that you use a manual VPATH methodology.
there are two approaches you can try:
1/ undo the unorthodoxy (move auto* files to top-level dir)
2/ prefix relative paths (such as ../../) w/
AFAIK There's a third possibility : you could setup a dist-hook target
in Makefile.am which allows you to specify completely your dist rule (I
had the same problem than yours and used this method). Unfortunately, it
also means that you might have to update this rule each time you change
metadata
... moving everything into the top-level dir (#1) did solve the
problem. Unfortunately, I don't currently have any control over the
directory structure (the motivation behind the attempt is to keep
platform specific items, i.e. *nix makefiles, VC++ 6 project files,
etc. in
On Tue, 9 Dec 2003, David Wolfe wrote:
AFAIK There's a third possibility : you could setup a dist-hook target
in Makefile.am which allows you to specify completely your dist rule
I suspect I'm too lazy for that. ;-) Seems like it would be more fun to
take a stab at hacking automake to
Hi All,
I posted a request for assistance a few days ago
(http://sources.redhat.com/ml/automake/2003-12/msg00042.html), and
although I realize this is a rather low volume list, I was hoping
someone would have responded by now. Was it an inappropriate post or
question? If so, could someone point
