make --win32 incorrectly handles PATH

Fri Jul 21 15:06:00 GMT 2000

On Fri, Jul 21, 2000 at 03:48:29PM -0600, Scott Carter wrote:
>On Friday, July 21, 2000 12:12 AM, Lassi A. Tuura wrote 
>>You could try something like
>> export PATH := $(PATH):$(EXTRA_PATH)
>>in your makefile.
>>>>I would expect that to do the right thing in unixy mode -- not having
>>the extra space and exporting the changed value to a subprocesses. 
>>Whether that will actually make it to %PATH% under Win32 I have 
>>no idea, and unfortunately can't test right now...
>>>I haven't put much into testing the unix mode cuz we don't use it. We
>selected the cygwin port of gnu make specifically because we wanted the
>increased Win/DOS compatibility we get in win32 mode. But since you
>mentioned it, I gave it a quick look-see.
>>Following your suggestion, in both unix and win32 modes I found that the
>form
> PATH +=xxx #(no space between = and x.)
>produces the extraneous space character I spoke of. But the form
> PATH := $(PATH):xxx #(with space after =.)
>does NOT produce the extraneous space. Interesting. That's a viable
>workaround for one of the problems.
>>I had tried export before, but tried it again now, just to verify. In unix
>mode, it's not needed for PATH, and seems to have no effect on Path. In
>win32 mode, using export (on PATH or Path) doesn't fix the problem.

I've finally taken the time to look at the make documentation, which is
an exercise that I would suggest for anyone who is trying to figure out
how a program works.
The usage
VAR +=something
is SUPPOSED TO ADD A SPACE TO VAR. So, make is working as documented
in this respect.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com