Thanks for your help. Now I have GNUstep installed on my home directory,
and I can work with it without conflict with my standar GNUstep
installation. Now I have another question. When I move the gnustep dir
to another place on my personal directory, I can work again with this
after change the paths on GNUstep.conf. But, as my target is make a
precompiled package, I would like the user just untar the app and he can
run this. Of course, I can set the appropriate paths with an script. But
there is a way to avoid this? The documentation say:
"If you wish to lock down a production system for distribution as a
relocatable package, so it can be installed anywhere, but users can't
accidentally change the config file and mess up paths, you can specify
the config file name as a path with a trailing slash so that the base
library will not read it, and will use the builtin default values.
To do this, you would configure using the options
--with-config-file=not-used/ and --with-default-file=myConfig where
myConfig is a file containing the paths you want to use relative to the
location the base library gets installed in."
First of all, I think is "--with-default-config=myConfig" not
"--with-default-file=myConfig". But this don't work to me. Maybe I
misunderstand this. myConfig can be placed in any dir, because only will
be used on the configuration, right? and the path of this file isn't
important. But now my question is about the relative paths. For example
if gnustep-base is installed on $HOME/MYGNUstep/Local/Libraries/ and the
apps on &HOME/MyGNUstep/Local/Applications. The relative paths to apps
would be:
../Applications
Or this is wrong?
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep