[ggo-discussion] Re: A few newbee questions

* Peter Strempel wrote on Sun, Oct 05, 2003 at 16:15 +0200:
> On Sun, Oct 05, 2003 at 05:01:38AM +0200, Steffen Dettmer wrote:
>=20
> > mmm... What's KDE? (just kidding)
>=20
> Windows for Linux. :*)

Ohh, it looks like a PlayStation or XBox Window Manager and as
WinXP looks like; I wonder if is displays a high score table
during shutdown :-)

> > When starting, I get a screen full of:
> > Failed to convert string to integer: java.lang.NumberFormatException: n=
ull
>=20
> gGo will save its configuration automatically to a config file $HOME/.ggo=
rc
> For whatever reason you already got such a file and it is messed. As resu=
lt,
> when gGo starts up it will read crap, print all these warnings you
> mentioned, and use its built-in default configuration.
>=20
> Solution: rm ~/.ggorc
> Restart gGo

With 0.4.0 I haven't tried it... Yep, I needed to kill the eSound
Daemon (already an FAQ IIRC :)) and it even finds gnugo by
default now :-) I disabled sound and now it runs. Thank you again
for your support. I feel more and more I choosed the subject with
care :-(

> You don't need to edit .ggorc manually or create it yourself, gGo takes c=
are
> of it.=20

Yep, works now. For some reason, it wasn't overwritten before (it
was empty/zero bytes size before).=20



glGo
----

> I would be interested in some feedback how glGo builds. The
> requirements are pretty tough, I used several libraries, mostly
> SDL stuff.=20

Well, this became a slighlty more compliciated operation as my
SDL and wxWindows are outdated and I need to update them first.
I did not use a CVS version. I write some ideas/comments; maybe
they are already fixed. I tried with glGo-0.0.5 sources.
(SourceForge-Download).

o wxGTK-2.4.2:

  ... hum, extra make in wxGTK-2.4.2/contrib/src/xrc required...
  (maybe worth an add-on in the README + some AC_CHECK_HEADERS? Or
  include new distributions this already?).=20

  --with-opengl seems to be important :-) The error I've got (some
  parse error due to undefined base class) needs some C++
  expiriences, maybe an AC_CHECK_HEADERS could get in here later or
  (as the header seems simply to define nothing) somethink like
  AC_TRY_COMPILE (or what the macro name was).



o SDL_gfx-2.0.8.tar.gz:

  I found out with google's help that this is simple another
  library.

  Then I needed to install "SDL_gfx-2.0.8.tar.gz".=20
  ./configure /usr/local/include/SDL
  (default path won't work, it's /usr/local/include).
  AC_CHECK_HEADERS for SDL_gfxPrimitives.h and
  SDL/SDL_gfxPrimitives.h?



o zziplib-0.10.82.tar.bz2:

  Then I needed to install "zziplib-0.10.82.tar.bz2".
  AC_CHECK_HEADERS?

  I got an linker error:
  /tmp/glgo/glGo-0.0.5/src/sdl/SDL_rwops_zzip.c:99: undefined
  reference to `zzip_open_ext_io64
  Well, libzzip issue? I tried "//#define USE_IO_EXT" in
  "SDL_rwops_zzip.c" without thinking.



o OpenAL:

  Then "openAL" was missing. As the the SuSE-Version won't
  work (maybe to old) and I saw no simple way of installing from
  source, I decided to use --disable-openal to your configure.



o plib:
 =20
  Then I needed to install "plib". AC_CHECK_HEADERS(plib/fnt.h)?



Sadly, the first attempt to run immediatly resulted in a SIGSEGV.
I'll sent the GDB stacktrace to you by PM.

> All required libs and headers are in my Debian distribution,

well, *Debian*... the distribution that is always up-to-date :)

> but I dont know if Suse 7.3 has them all. The README file has a
> chapter about compiling, list what you need.  The very latest
> configure script (I am committing it into the sourceforge CVS
> right now) has some additional checks if the required headers
> are present.

I wanted to try the "released" 0.0.5 first. Do you recommend to
try also the CVS version?

> > Thank you. BTW, autoconf/automake (especially autoconf) is always
> > a mess, isn't it :) ? But still the best tool out there I think...
>=20
> autoMAKE is actually not bad, but I regulary get the creeps
> when I need to write some m4 macros for autoCONF. M4 looks
> slightly old. :)

yeah, a very cool thing is for example, that autoconf redefines
the M4 quoting characters... Then there are limitations (such as
conditional AC_SUBST won't work, many macros cannot be used
twice, which may get complicated in modular .m4 file) and heavy
changes between 1.4 and 1.7. If it builds with 1.4 on linux,
build surely will fail on cygwin 1.7 :-) Maybe its for geniuses
:-)

oki,

Steffen

--=20
Dieses Schreiben wurde maschinell erstellt,
es tr=E4gt daher weder Unterschrift noch Siegel.

Other related posts: