[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 around all macro expansions where one path name is known to
>> be expanded (as in "$(CLEARTOOL)" in your example). But what do you do
>> with $^, for instance?
>
>For what it's worth, our toplevel makefile (actually our platform
>description, following "Applying RCS and SCCS" by Bolinger and Bronson)
>defines an acceptable quote character for the shell (on Windows you have
>QUOTE='; on pretty much anything POSIX you have QUOTE="). Then our
>(say) install targets look something like this:
>
> install : $(VARIOUS_FILES)
> $(INSTALL) $(foreach file,$^,$(QUOTE)$(file)$(QUOTE))
>$(INSTALLDIR)
>
>The same platform description of course would cause $(INSTALL) to be,
>say, "copy" or "xcopy" or some such on Windows and "cp" or "install"
>everywhere else.
Which quote and tools to use isn't a problem here since we use tools that make
Windows act more like Unix.
Noel
PS
IMHO, "Applying RCS and SCCS" had a lot of stuff I disagreed with. I haven't
looked at the book in a while, so I've forgotten what those issues were. IIRC,
one of them might've been its support for recursive makes.
Noel
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
