[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: creating library - some other [4] questions from newbie

From: Nicola Pero
Subject: Re: creating library - some other [4] questions from newbie
Date: Wed, 8 Aug 2001 11:39:05 +0100 (BST)


> > > ... ProjectCenter compilation problem ...
> > > You need to compile/install PCLib first.
>       Yes, I have had exactly the same problem on RedHat 7.0
> ???   Are sources of the ProjectCenter in some CVS? [I can't find it on
>               cvs -z3 -d :pserver:address@hidden:/cvsroot update core
>               cvs -z3 -d :pserver:address@hidden:/cvsroot update dev-apps
>               cvs -z3 -d :pserver:address@hidden:/cvsroot update dev-libs


cvs -z3 -d :pserver:address@hidden:/cvsroot update -Pd dev-apps

please note the `-Pd' which tells CVS to remove empty dirs, and get new

> [1] I have configured, built and installed `/opt/dev-libs/guile'
> project, according
>       to `INSTALL' file, I have tried `make check' and I have got this
> messages
> --------------------------------------------------------------------------------------------
> address@hidden guile]# make check
> Making check in Greg...
> WARNING: No GNUmakefile found for subproject Greg; using 'Makefile'
> make[1]: Entering directory `/opt/dev-libs/guile/Greg'
> (cd Test; make check);
> make[2]: Entering directory `/opt/dev-libs/guile/Greg/Test'
> greg --tool basic
> ERROR: In procedure dynamic-link:
> ERROR: file not found
> make[2]: *** [check] Error 2
> make[2]: Leaving directory `/opt/dev-libs/guile/Greg/Test'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/opt/dev-libs/guile/Greg'
> make: *** [internal-check] Error 2
> --------------------------------------------------------------------------------------------
>       what's wrong?

Well - I'm not sure :-) - the error message is not particularly clear - so
the best I can do is asking the usual trivial questions - have you
installed gnustep-guile before doing make check ?  Have you run the
gnustep configuration script before doing make check ?  Otherwise, you
probably need to find out more about the error to allow us to help
you.  It looks like guile can't find the guile-gnustep libraries or
something, so it might be a problem with LD_LIBRARY_PATH, but it should be
set up correctly by GNUstep.sh.  Try adding
to your ld.so.conf...

Btw, yes, it works on my system. :-)

> [2]
> what are backends,
> why when I am using `gnustep-xdps' windows of the GNUstep applications
>         are at first blank and only after some operation with these
>         windows [clicking on them to open other windows], they stop
>         to be blank and paint themselves somehow

> why when I am using `gnustep-xgps' even thogh works far better than
>       `gnustep-xdps' [on my machine] windows of the GNUstep applicatoins 
>       first paints themselves white and only after that thay paint themselves
>       as required - is that painting whole window white necessary - it causes
>       flickering [which does not occur in the other X-applications under
> WindowMaker]

Yes - the major thing for speeding up the backend is studying exactly how
the drawing is done and making sure things are drawn only once.  That
would also remove annoying flickering which is definitely there on slower
computers.  Well - I hope I sort-of-answered your question :-)

> [3] - another TYPO [easy] in the tutorial
> `www.gnustep.it/nicola/Tutorials/MoreOnMakefiles/node5.html'
>       in first program, there is a line
>               #include <HelloWorld/HelloWorld.h>
>       I think it should to be
>               #import <HelloWorld.h>

Ahm - thanks - I noticed that when fixing the tutorial the other time - I
think I already fixed that - in the new version of the tutorial the
GNUmakefile for the library has been modified to contain

libHelloWorld_HEADER_FILES_INSTALL_DIR = /HelloWorld

if you install the library using this new GNUmakefile, it should work with
#include <HelloWorld/HelloWorl.h>

> [4] - compilation of the `/opt/core/base/Testing' goes without problems,
> tools which can be built there
>       work well [I think one of them throws uncaught exception but ...]
>       but compilation of the `/opt/core/gui/Testing' ends with these
> messages:
> [snip]
>       ??? what's wrong? ... I would like to compile these testing
> applications, because
> it may contain valuable source code [for beginner]. 

Ok - I will have a look at the directory when I got time - but - *warm
suggestion* - that directory is basically unused/obsolete - if you are
looking for example/testing code, you better check-out the real one 


(have a look at

which contains a gui directory with quite a lot of example code.  If you
find anything wrong in the examples directory, please report it ! you're
welcome, we'll try to fix it, that one is the currently maintained `gui
examples' directory.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]