Re: PATCH: NSPathUtilities etc

[Roland Schwingel]

Hi... :-)

A quick answer, I nearly have no time on my keyboard today and tomorrow...

> Let me address you concerns en-block, rather than in response to each
> paragraph. It'll make my response much more coherent.
>
> Firstly, GNUstep under windows current requires setting
> GNUSTEP_SYSTEM_ROOT as
> an environment variable. If it's not set, it defaults to the build
variable
> GNUSTEP_INSTALL_PREFIX {which is usually "C:\GNUstep" from memory.}
> So, if your applications are simply drag-installed they _all_ will have
the
> _same_ GNUSTEP_SYSTEM_ROOT. Doesn't matter which directory you've
installed
> them into.
> I believe that you are confusing the SYSTEM_ROOT path with the
> ability to load
> Bundles from the application directory. The Bundle loading system hasn't
been
> changed (and won't be). The mod only adds a missing feature which was
loading
> Frameworks from any directory in the domain heirarchy. It's been marked
as a
> FIXME for a while now...
Well... It is a little bit different here... You can live without setting
explicitly $GNUSTEP_SYSTEM_ROOT (or any other GNUSTEP environment variable)
at all. GNUSTEP will run fine. We start our Applications (which require
GNUstep) indirectly, means there is a small C only exe (called launcher)
that searches for a GNUstep folder relativ to its own location and then
sets GNUSTEP_SYSTEM_ROOT (and other variables like $PATH to find the
.dll's).
Afterwards it start another exe located on the same level as the launcher
which is the "real" executable which then uses GNUstep/objc etc.

This way you can most easily deploy GNUstep applications which will not
require any installation stuff, making eg. network installation effortless.
Just copy the .app whereever you like it to have. This is (nearly) the same
as NeXT did (and Apple is doing often todays). You can easily relocate
apps by just moving them around.

Regards,

Roland (on the run).