I'm an expert to the untrained eye ;^)
Most of the time I just stare at things really hard, read a few man/info
pages, experiment - then a miracle occurs - it works.
Sure. I'/ve been playing with GGI for years and have been a lurker for
years. I've always wanted GGI to go places so nows my chance to help.
I'll do it!
On 05 Jul 2001 17:45:17 +0200, Christoph Egger wrote:
> On 5 Jul 2001, Thayne Harbaugh wrote:
>
> > I should have explained this better. The whole idea behind libtool is
> > that it takes care of the libraries for you, makes things portable, and
> > you can ignore all the nasty details. Specifying -L../gg/.libs is
> > intruding on libtools job - it is the one stashing libs in the .libs
> > directory and libtool is supposed to make things work on the surface as
> > things would be expected to work without it. If your libtool is correct
> > then "-L../gg" is sufficient.
>
>
> Well, I have two different libtool versions on my system. The
> system-wide one (which is 1.2f) and the one coming with each GGI-lib
> (toplevel -directory ltmain.sh -file; version 1.3.5).
>
> When building always the last one is used. I get a "can't find -lgg"
> error, when compiling libgii. So I think, we must update our libtool
> everywhere.
>
> Thayne: You seem to be an expert for that stuff. Would you like to
> maintain the whole building-system?
> We really need an autoconf/automake/libtool expert since Marcus
> Sundberg is extremely quiet. Of course, we will help you as much as
> possible. You'll also get CVS access then, of course (only
> SourceForge registration is required by you for this).
>
>
> CU,
>
> Christoph Egger
> E-Mail: [EMAIL PROTECTED]
--
Thayne Harbaugh
Your eyes are weary from staring at the CRT. You feel sleepy. Notice how
restful it is to watch the cursor blink. Close your eyes. The opinions
stated above are yours. You cannot imagine why you ever felt otherwise.
