Re: GNUstep.conf problem

[Richard Frith-Macdonald]

I've committed some more changes/fixes to the base library to try to  
make this config stuff as easy as possible.

You should be aware that, while make and base use the same config  
under unix-like systems, they need different config under windows.   
This is because the build environment msys and makefiles etc uses  
unix style paths (they don't like backslashes, spaces, or colons),   
but tools/applications are supposed to use native windows paths (ie  
with colons and backslashes)

So, on mingw the make package should use /c/GNUstep/GNUstep.conf-dev  
as the config file, but the base package should now use that file  
*only* to for building/installing the base library.

By default on mingw, the base package now uses './GNUstep.conf' as  
the configuration file location (which means it expects the config  
file to be in the same directory as the base library DLL).  It also  
now has built-in default locations (used when no config file is found  
at runtime) which should find all resources relative to the location  
of the library DLL.

Distribution of a package where everything is in one directory should  
be possible simply by putting a GNUstep.conf in that directory with  
the appropriate values ('GNUSTEP_SYSTEM_ROOT=./' etc).  I haven't  
actually tested that though.

Of course, what I've just described is the default setup ... there  
are various options to the configure script which can be used to  
override this setup in various ways.  What I've tried to do is ensure  
that the default setup is very easy to work with.

On 5 Jan 2006, at 02:54, Lloyd Dupont wrote:

> I was about to do Tortoise CVS => History, very easy, one click!
> But the CVS conf has changed.....
> Well it's pretty hectic, I sure will checkout CVS again.. in 2  
> weeks from now..
>
> Regards,
> Lloyd Dupont
>
> NovaMind development team
> NovaMind Software
> Mind Mapping Software
> <www.nova-mind.com>
> ----- Original Message ----- From: "Sheldon Gill"  
> <sheldon@westnet.net.au>
> To: "Lloyd Dupont" <lloyd@nova-mind.com>
> Cc: "GNUstep Discussion" <discuss-gnustep@gnu.org>
> Sent: Thursday, January 05, 2006 12:33 PM
> Subject: Re: GNUstep.conf problem
>
>
> > Lloyd Dupont wrote:
> > > Actually I have to point to the GNUstep.conf file with the env  
> > > variable 'GNUSTEP_CONFIG_FILE'
> > >
> > > When I tried to:
> > > - ensure this variable was empty
> > > - the GNUstep.conf file in my running directory
> > > it didn't work.
> >
> > Funny you mention it today. I've just been testing base-1.11.2 and  
> > discovering a number of issues.
> >
> > Using the GNUStep.conf file in your running directory requires  
> > "./" at the start of the path specification. You'll have to  
> > rebuild base to change that.
> >
> > > I have a CVS version from around end of november 2005.
> > > Was it a bug?
> > > In which cases has it been fixed?
> >
> > Check your version of NSPathUtilities.m against the lastest.  
> > Probably easiest to use your web browser to view and visually  
> > compare instead of checking out.
> >
> >
> > Regards,
> > Sheldon
>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnustep