On 6 Dec 2005, at 06:49, Lloyd Dupont wrote:
It's why I was (unsuccessfully :-( ) suggesting to have the
GNUstep.conf file in this directory.
I don't understand this last comment ... what is it that doesn't
work when you put the GNUstep.conf file and the gnustep-base dll
in the same directory? I'm moderately sure I tested that
configuration on mingw (not just on unix) a few weeks ago, before
my machine died.
hu...
I didn't try...
but according to my understanding of what you said.
this would never be implemented.
I have no idea how I managed to give that impression ... that's one
of the main ways the configuration system is *designed* to work.
Now if I get this email correctly that should, in fact, work?
mhh... I have to give it a try then!
Could I use a path like that in the GNUstep.conf then:
GNUSTEP_SYSTEM_ROOT=./../GNUstep
Yes.
I think that 'GNUSTEP_SYSTEM_ROOT=./System' would be more normal
though ... it says that the System domain is the 'System'
subdirectory of the directory containing the config file.
You configure the base library with './configure --with-config-file=./
GNUstep.conf' to tell it to look for the config file in the same
directory as the DLL.
do you think this behavior of:
1. using a GNUstep.conf file (in the same directory as the dlls)
2. specifying path starting with "./"
is here to stay?
Yes ... it's a core design feature of the new config file system ...
ie. one of our key objectives designing it was to make creation of
relocatable packages for windows easy.
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
