Follow-up Comment #3, bug #15720 (project make):
Indeed you're correct. My Win32 build of GNU make 3.81beta4 detects my Cygwin
sh.exe automatically and makes use of it without a warning. Mixing Cygwin
sh.exe with non-Cygwin app such as win32-make.exe can be problematic.
So I wrote a simple Bourne Shell simulator in Perl, and instructed `make' to
use that, and variable exporting turns right since then:
C:\Temp>type Makefile
bar: export foo := foo
bar: ; @echo $(foo) $$foo
C:\Temp>win32-make
foo
C:\Temp>win32-make "SHELL = perl G:\script\sh"
foo foo
However, I can't simply move the `perl G:\script\sh' thing from command line
into the Makefile itself because of [bug #15718]. The screen-shot is as
follows:
C:\Temp>type Makefile
SHELL = perl G:\script\sh
bar: export foo := foo
bar: ; @echo $(foo) $$foo
C:\Temp>win32-make
foo
> P.S. Please don't assume that people who worfk
> on the Windows port don't run the test suite.
> I ran the entire test suite when I built the
> last beta, and everything worked as expected.
Glad you run the test suit as me. :=) That was solely a bad joke, please
don't take it personally. I appologize for my rudeness.
Frankly speeking, the Win32 port of `make' is cute. You all have done a good
job.
Blessings,
Agent
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=15720>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
