Ralf Wildenhues writes:
>> I don't know what limitation you refer to. Can you please explain how
>> make's design causes these problems?
>
> Well, at least white space in targets and dependencies is forbidden
> with make.
Whitespace can be quoted with '\'. At least in GNU Make, the following
* John Calcote wrote on Fri, May 16, 2008 at 11:00:40PM CEST:
> EXTRA_DIST = greptest.sh
> TESTS = greptest.sh
>
> But this requires me to:
>
> 1) Actually HAVE a one-line script file called "greptest.sh" as part of
> my package.
>
> 2) Use the EXTRA_DIST line. Why is this? Can't Automake tell f
* Peter Simons wrote on Sun, May 18, 2008 at 01:29:47PM CEST:
> Bob Proulx writes:
>
> > This leads to 'make' not being designed to handle filenames with
> > whitespace and of course automake tries to produce portable make
> > configurations.
>
> I don't know what limitation you refer to. Can
Hi Peter,
* Peter Simons wrote on Sat, May 17, 2008 at 06:07:39PM CEST:
> I just ran across an interesting problem with automake 1.10. Just unpack
> any other build into a directory called, say "/tmp/test automake", and
> run it. In my particular case, the makefiles failed to call the local
> copy
Hi Stepan,
first of all, thank you very much for your insightful response. I
appreciate that you've taken so much time to help me with this issue. I
chose this approach to solve my doxygen problem:
> [2] You can avoid running your "html-local" within the distcheck.
I'm glad that using this tech
Bob Proulx writes:
>> [Unpack] any other build into a directory called, say "/tmp/test
>> automake", and run it. In my particular case, the makefiles failed
>> to call the local copy of install-sh because of the blank.
>
> This is a documented limitation. See the following reference.
>
>
