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 -- wh
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
"C:/Pr
David Boyce writes:
> For the record, there's one option you haven't discussed:
>
> CLEARTOOL := C:/Progra~1/Rational/ClearCase/bin/cleartool.exe
That can't be guaranteed to be correct across multiple machines. If
another "long" filename beginning with "Progra" was created on the disk
prior to t
For the record, there's one option you haven't discussed:
CLEARTOOL := C:/Progra~1/Rational/ClearCase/bin/cleartool.exe
However, I think getting rid of the full path is the more robust solution.
-dsb
At 09:38 AM 7/28/00 -0400, Noel L Yap wrote:
>[EMAIL PROTECTED] on 2000.07.28 02:07:41
> >Tal
Wolfgang Laun wrote:
> Nice, but how do you set VARIOUS_FILES when your file names have
> embedded spaces?
Yeah, this is a problem you can't get around without intervention.
Cheers,
Laird
[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 q
[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 expansi
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 n
Noel L Yap wrote:
>
> With the advent of (idiotic) paths with spaces in them, it's become important to
> deal with them.
>
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 gene
