discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ANN: New Windows Installer now with GUI!


From: Alex Perez
Subject: Re: ANN: New Windows Installer now with GUI!
Date: Fri, 25 Feb 2005 16:30:29 -0800
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Pablo Di Noto wrote:

Alex Perez escribió:

Marko Riedel wrote:

Hello there,

I tried the installer. Everything went fine. Next I tried to compile
my mastermind program. I was logged on as "riedel." I had to edit the
makefile and replace

$(GNUSTEP_SYSTEM_ROOT)/Makefiles

by

$(GNUSTEP_SYSTEM_ROOT)/Library/Makefiles



Actually, you really need to be using $GNUSTEP_MAKEFILES. This is much safer.


In my case, using the installer with precompiled binaries on WinXP Prof + SP1, I get the same error.

But as I can see, the environment variable $GNUSTEP_MAKEFILES correctly points to $(GNUSTEP_SYSTEM_ROOT)/Library/Makefiles, but GNUmakefile insists in looking at $(GNUSTEP_SYSTEM_ROOT)/Makefiles. May be it is (incorrectly) hardcoded?

Yes, this is my point. It's a shame marko never replied... :(


$ export PS1="\u@\h \w # "
Pablo@AVENTIUM ~ # cd /c/GNUstep/Test/
Pablo@AVENTIUM /c/GNUstep/Test # cd GConnectFour/
/c/GNUstep/Test/GConnectFour
Pablo@AVENTIUM /c/GNUstep/Test/GConnectFour # make
GNUmakefile:6: /c/GNUstep/System/Makefiles/common.make: No such file or directory GNUmakefile:26: /c/GNUstep/System/Makefiles/application.make: No such file or directory make: *** No rule to make target `/c/GNUstep/System/Makefiles/application.make'. Stop. Pablo@AVENTIUM /c/GNUstep/Test/GConnectFour # ls -l /c/GNUstep/System/Makefiles
ls: /c/GNUstep/System/Makefiles: No such file or directory
Pablo@AVENTIUM /c/GNUstep/Test/GConnectFour # echo $GNUSTEP_MAKEFILES /c/GNUstep/System/Library/Makefiles


In my case, copying the Makefiles directory where GNUmakefile expects it worked (not very nice, I know).

Don't do that. The reason he's using $GNUSTEP_SYSTEM_ROOT/Makefiles is (A) They used to live there, a while back, and (B) There's a symbolic link there under *NIX. If he were using the envvar he should have always been using, then we would not be having this conversation.


Regards,
///Pablo






reply via email to

[Prev in Thread] Current Thread [Next in Thread]