Wolfgang Laun wrote:
Talking about UNIX (vanilla) Make and GNU Make, I'd say that you're in
for some fun and games if you try to make this robust against spaces in
path names by using some general set of rules. It would be possible to
put quotes around all macro expansions where one path name
[EMAIL PROTECTED] on 2000.07.28 02:07:41
Talking about UNIX (vanilla) Make and GNU Make, I'd say that you're in
for some fun and games if you try to make this robust against spaces in
path names by using some general set of rules. It would be possible to
put quotes around all macro expansions
[EMAIL PROTECTED] on 2000.07.28 09:22:26
Wolfgang Laun wrote:
Talking about UNIX (vanilla) Make and GNU Make, I'd say that you're in
for some fun and games if you try to make this robust against spaces in
path names by using some general set of rules. It would be possible to
put quotes
Did I say it was guaranteed to be correct? No, in fact in the very next
breath I promoted another solution as being more robust. Note that none of
the solutions mentioned are guaranteed to work; e.g. the CC installation
allows the default installation path to be changed, so depending on
On Fri, Jul 28, 2000 at 02:38:12PM -0400, Laine Stump wrote:
David Boyce writes:
CLEARTOOL := C:/Progra~1/Rational/ClearCase/bin/cleartool.exe
That can't be guaranteed to be correct across multiple machines.
Or indeed within the same machine, if you ever have to do a full
restore -- which
With the advent of (idiotic) paths with spaces in them, it's become important to
deal with them.
I was thinking of the following style rule for calling executables:
1. When calling executables, wrap the executable name in double quotes. This is
even more important if a macro is being used
[ On Thursday, July 27, 2000 at 16:52:59 (-0400), Noel L Yap wrote: ]
Subject: general makefile (and script) style rule
Aside from "preventing" (ie ignoring) the problem, has anyone else found a good
way to deal with the situation?
Proactively seeking them out and destroying them
