Re: ANN: GWorkspace 0.6.5

[Enrico Sersale]

On 2004-06-05 00:58:21 +0300 Alex Perez <aperez@student.santarosa.edu> wrote:

> Enrico Sersale wrote:
>
> > GWorkspace has been splitted in some applications, Desktop, Inspector, 
> > Finder, Operation and the file viewers, represented by the old GWorkspace 
> > application itself.
> > This is a transition release because also the file viewers will be rewritten 
> > soon.
> > But, for the moment, I want to release this work because I've written many 
> > new parts that must be tested.
> >
> > Some parts needs the new FSNode framework, a collection of classes that 
> > encapsulates many NSFileManager and NSWorkspace methods in a simplier API 
> > and offers some basical elements to represent files, as icons, icons views, 
> > browser cells, etc.
> > So, you need to install it first:
> >
> >      cd FSNode
> >      make install
>   From a packaging point of view (and also from a style point of view) this 
> build method is unacceptable. This is exactly what Michael Baehr was talking 
> about a mere day or two ago. *EVERYTHING* should build from the root of a 
> project directory as long as you have your makefile set up properly with 
> subprojects; Your makefiles are not set up correctly. If you need some help 
> getting this set up properly, I'm sure either Michael or myself will be 
> willing to help you with it. Please do not assume that the only people using 
> your program will be compiling it from source. We're making a concerted 
> effort out of trying to automate package generation, and GWorkspace and other 
> great applications like it are compromising our ability to do so.  Don't take 
> this as a personal attack, Enrico, but we're feeling rather frustrated that 
> certain bad assumptions are being made, and we feel it's high time to raise 
> our concerns.

No problem Alex, I know that this is not personal attack :-)
Till now GWorkspace has built with a simple ./configure (to detect the presence 
of PDFKit and of two or three other things) and a make install.
Now this problem has appeared because I've decided to make FSNode a framework 
instead of a library and, evidently, beeing the first time I use this solution, 
I'm not able to link against it before installing. (It must be said, anyway, 
that there are not too many examples to copy from...)
So, if you or Michael want to help me, this is certainly welcome.
Else, the faster solution I see, is to build FSNode as a library and to add to 
the various makefiles of the subprojects a -I../FSNode and a 
-L../FSNode/$(GNUSTEP_OBJ_DIR).

> > then you can build the other things:
> >
> >      cd ../
> >      ./configure
> >      make install
>
> See above.
>
> Cheers,
> Alex Perez
> GNUstep.org co-maintainer and
> Unofficial Packaging Bitch
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnustep