bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] 3d board


From: Jim Segrave
Subject: Re: [Bug-gnubg] 3d board
Date: Wed, 13 Aug 2003 17:32:41 +0200
User-agent: Mutt/1.4i

On Wed 13 Aug 2003 (14:29 +0000), Jonathan Kinsey wrote:
> 
> >From: Jim Segrave <address@hidden>
> >
> >Can we please have a configure flag which completely negates this
> >option and uses the previous ?
> 
> The code is removed if USE_BOARD3D isn't defined.

But it tries to compile drawboard3d.c

after complaining about TRUE and FALSE being re-defined between
config.h and /usr/local/include/glib-2.0/glib/gmacros.h, it then dies
with:

In file included from drawboard3d.c:30:
inc3d.h:83: parse error before "Material"
inc3d.h:84: parse error before '*' token
inc3d.h:85: parse error before '*' token
inc3d.h:86: parse error before '*' token
inc3d.h:87: parse error before '*' token
inc3d.h:92: parse error before "Path"
inc3d.h:93: parse error before '*' token
inc3d.h:94: parse error before '*' token

(a minor nit - there are a lot of C++ style comments. It's not safe to
assume that a C compiler will accept these).

I think people without the 3d libraries are going to have some
problems building.

> >Under FreeBSD, all animation is completely stopped. This makes games
> >unplayable.
> 
> Have you any ideas on this?

Not really - it appears to spend all it's time in the thread scheduler
without actually doing anything. Short of trying to rebuild all of the
libraries involved with debugging symbols, no, I don't have an
idea. I'll be curious to see if Holger can get it running under
Solaris or if the MAC-OS versions work with this
 
> >Under Linux, on a Dell L-400 laptop 700Mhz CPU, a simple move will
> >take between 30 seconds and one minute to animate, as it has no
> >hardware acceleration. This makes games unplayable.
> 
> Surely it only effects the 3d board?  i.e. can't you just switch to 2d?

Probably, but as the machine is not at hand at the moment, I can't
verify that.

-- 
Jim Segrave           address@hidden




reply via email to

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