>> **1. No more need to source GNUstep.sh :-)
>>
>> It works for me, might need more work to work for everyone I guess ;-)
>>
>> Anyway in the standard flattened/no-multi-arch case, once I add the
gnustep dirs
>> to /etc/ld.so.conf and to PATH (I'm on GNU), I can now compile stuff by
>> just doing:
>>
>> export GNUSTEP_MAKEFILES=/opt/gnustep/System/Library/Makefiles
>> make
>>
>> No more need to source GNUstep.sh :-)
>> (hope it works for you as well, if not, let me know!)
>
> I'm afraid that won't work on MS-Windows. For starters, no /etc/ld.so.conf
>
> Also, I'm not that keen on adding all those dirs to either ld.so.conf or
my PATH.
Ahm - but if you don't add them to ld.so.conf or PATH, how can you run
GNUstep
apps ? ;-)
I suppose you have to source GNUstep.sh before every compilation and also
before running every tool or application ... that is still a perfectly
valid option if you like it! ;-)
I just wanted to mention that for GNU/Linux guys that are looking for a more
traditional Unix approach (we had millions of requests for this), that
approach
is now available ...
1. add /usr/GNUstep/System/Library/Libraries
and /usr/GNUstep/Local/Library/Libraries to your ld.so.conf
2. add /usr/GNUstep/System/Tools and /usr/GNUstep/Local/Tools to your PATH
That should be enough for running stuff; binary packages can automatically
do 1. and 2.
and GNUstep stuff will run natively as any other system binary (of course,
GNUstep.conf
should be installed into /etc/). :-)
Developers who want to compile stuff just need to add an additional step --
3. set GNUSTEP_MAKEFILES if you are compiling anything (ie, export
GNUSTEP_MAKEFILES=...)
Unfortunately, there isn't much hope of getting away without 3. simply
because all GNUmakefiles
start with
include $(GNUSTEP_MAKEFILES)/common.make
and unless GNUSTEP_MAKEFILES is defined, this won't work.
Of course you can still source GNUstep.sh in some way, I appreciate your
point that setting
GNUSTEP_MAKEFILES is still a single line of bash code, the same number of
lines as sourcing
GNUstep.sh ;-)
> Also, your solution *still* requires
>
> export GNUSTEP_MAKEFILES=
>
> which sort of defeats the purpose in my view because you still need a
> preliminary step before you can build.
Maybe you are right. I find it simpler that setting a single variable is
enough
to build, but I suppose that's a matter of perception ;-)
(btw -- if you install gnustep-make in '/', then you don't even need
to set GNUSTEP_MAKEFILES! [just joking] ;-))
> Hmm.. won't this will mean that all Headers will actually be in
>
> $GNUSTEP_SYSTEM_ROOT/Library/Headers/${ac_cv_library_combo}
>
> right? So we'd have like
>
> /usr/GNUstep/System/Library/Headers/gnu-gnu-gnu/Foundation/
>
Yes.
Thanks
_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
