Re: gstep-base...

[richard]

On Tuesday, November 7, 2000, at 09:16 AM, kevin@suberic.net wrote:

> ok, i downloaded gstep-base 0.6.6 from ftp.gnustep.org onto a 
> pretty vanilla redhat linux 6.1 box.  i'm not actually interested 
> in gnustep but in objective c.  libobject was recommended and i slowly 
> learned that it has been folded into gstep-base. 
>
> fine. 
>  
> so i run configure and it configure's correctly and then i run make: 
>  
>     make: *** No rule to make target `/Makefiles/aggregate.make'.  Stop. 
>  
> hm.  download gstep-make 0.6.6, configure, make, install.  delete the 
> gstep-base directory, untar it again, configure, make: 
>  
>     make: *** No rule to make target `/Makefiles/aggregate.make'.  Stop. 
>  
> right.  at this point i read the INSTALL and README files.  both point me 
> to GNUstep-HOWTO.  i run "find . -name GNUstep-HOWTO\* -print" in both 
> directories.  nope. 

The GNUstep-HOWTO file is in the core directory and online at www.gnustep.org
(you can find it by following the documentation link from the front page).

1. You need to configure, build, and install gstep-make
2. You need to set up your environment 
  $ . /usr/GNUstep/System/Makefiles/GNUstep.sh
3. You need to configure, build, and install gstep-base
4. You can now play with it all - but remember always to use GNUstep.sh
to set up your environment before working with GNUstep.

> i'll keep going on this, and perhaps i'll come up with patches or 
> something, but please consider that the more people that use your class 
> library - even if not in gnustep - the better it will be in terms of 
> features and stability.  in fact if i use objective c like i'm considering 
> i'll probably look for performance tweaks on lower level objects. 

That would be good - but please work with the latest code from the CVS 
repository
if you are intending to do that sort of thing - patches from the 0.6.6 release
might be difficult to apply sinec there have been a fairly large number of
optimisations and tidyups since then.

> and since it might be used outside of gnustep, perhaps it might be wise to 
> consider not requiring gnustep. 

Depends what you mean by gnustep - to some people, the base library and makefile
package *is* gnustep.
Currently the main package is 'core' - the basic libraries and tools needed to
develop gui applications.
Hopefully there will soon be a minimal package containing gstep-base and 
gstep-make -
enough to develop command-line applications.
There is also a sort of kitchen-sink package under development, a GNU/Linux 
distribution
based around all the GNUstep libraries and containing a number of applications.