[Top][All Lists]

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

Re: ANN: Build Guide version 2.0.0

From: Dennis Leeuw
Subject: Re: ANN: Build Guide version 2.0.0
Date: Wed, 05 Dec 2007 18:19:29 +0100
User-agent: Icedove (X11/20071018)

Nicola Pero wrote:
GNUSTEP_*_ROOT variables obsolete with gnustep-make 2.x? Some projects
have bugs in their makefiles because the way variables are used have
changed over time, and it would help if the build guide didn't
encourage use of legacy variables.
yes and no. True if they where not needed, but since I make the users compile everything in /usr/GNUstep there needs to be some way to tell where everything is. So there are two approaches (imho):

1) Set PATH and LD_LIBRARY_PATH (ld.so.conf is linux specific afaik and I don't know all the options for other flavours of unix).

2) source GNUstep.sh and have it that solve the problem.

Dennis, your plan looks very good :-)

I imagine Truls was referring to your startup scripts where you use GNUSTEP_SYSTEM_ROOT and other variables that are considered obsolete
in gnustep-make v2.0 ... you may want to make your scripts more robust
(and more future-proof, not to talk encouraging new users/developers
to use the new, more powerful and general variables) by replacing these with non-obsolete variables. ;-)

Eg, if you want to run gdomap, instead of


you can now simply do


So I tried to figure out what the options are... but now I am confused...

$ . /usr/GNUstep2/System/Library/Makefiles/GNUstep-reset.sh
$ . /usr/GNUstep2/System/Library/Makefiles/GNUstep.sh

There is no GNUSTEP_SYSTEM_TOOLS variable to use... am I missing something? There is no way from the variables set by GNUstep.sh to know where the GNUstep.conf file is, so that won't help too. So the question is:

When I have a cleanly booted system, where GNUstep is installed in /usr/GNUstep is there a way to figure out how to set everything up. I could just make every user set his or her GNUstep.conf in the script, but the current scripts are without human intervention when you install in the default directory.

Think I need to sleep on this one, to see how to solve it. Any good ideas are highly appreciated.


In fact, what about just doing 'gdomap' ?  If you source GNUstep.sh, gdomap
will be in your PATH so there is nothing to do (unless you are trying to
avoid conflicting with an existing 'gdomap' on the system ?). :-)

Anyhow, I'm including here the entire 'RELEASENOTES' file from gnustep-make 
Have a look and see if it helps you.  Remember that even if you are using and
recommending the gnustep-layout (which is a very nice layout!) we're trying to
move everyone to the situation where the same software/scripts/etc. will work
on all types of layout that GNUstep supports.  So it's important to update to
use the new variables ;-)


reply via email to

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