Page 1 of 1

xboard gtk

PostPosted: 08 Sep 2009, 14:42
by bodiless
I am not sure if I should post this here but I didn't wanted to subscribe to the xboard-devel mailing list just for one post.

Anyway, after the release of vs 4.4 and reading through the older posts I got a bit currious how the gtk version would look like. After solving various other problems and dependencies I am getting stuck when I run make, which returns the following error:

Code: Select all
root@siduxbox:/home/nikos/Desktop/xboard-gtk# make
make  all-am
make[1]: Entering directory `/home/nikos/Desktop/xboard-gtk'
gcc -DHAVE_CONFIG_H -I.  -DINFODIR='"/usr/local/share/info"' -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include      -MT xboard.o -MD -MP -MF .deps/xboard.Tpo -c -o xboard.o xboard.c
In file included from xboard.c:182:
bitmaps/bitmaps.h:470: warning: excess elements in array initializer
bitmaps/bitmaps.h:470: warning: (near initialization for ‘builtInBits[5].bits’)
bitmaps/bitmaps.h:490: error: ‘wp_72s_bits’ undeclared here (not in a function)
bitmaps/bitmaps.h:490: error: ‘wn_72s_bits’ undeclared here (not in a function)
bitmaps/bitmaps.h:490: error: ‘ws_72s_bits’ undeclared here (not in a function)
bitmaps/bitmaps.h:490: error: ‘wl_72s_bits’ undeclared here (not in a function)
bitmaps/bitmaps.h:491: error: ‘wp_72o_bits’ undeclared here (not in a function)
bitmaps/bitmaps.h:491: error: ‘wn_72o_bits’ undeclared here (not in a function)
bitmaps/bitmaps.h:491: error: ‘ws_72o_bits’ undeclared here (not in a function)
bitmaps/bitmaps.h:491: error: ‘wl_72o_bits’ undeclared here (not in a function)
xboard.c: In function ‘InitDrawingSizes’:
xboard.c:2091: error: subscripted value is neither array nor pointer
xboard.c:2091: warning: assignment makes integer from pointer without a cast
make[1]: *** [xboard.o] Error 1
make[1]: Leaving directory `/home/nikos/Desktop/xboard-gtk'
make: *** [all] Error 2

Anybody understand what I need to do?

Re: xboard gtk

PostPosted: 08 Sep 2009, 17:14
by H.G.Muller
It seems that the file bitmaps/bitmaps.h contains genuine errors: a number of symbols are defined with an extra underscore in front of the 72 which is not supposed to be there. (I.e. wp_72s_bits.h in stead of wp72s_bits.h.)

I guess Arun does not notice this when he compiles, because the bitmaps are only optionally included in the compile, when the compiler switch HAVE_LIBXPM is false. When this swicth (set by the configure process) is true, XBoard uses built-in pixmaps rather than (monochrome) bitmaps.

So possible solutions are:
1) try to figure out why you don't have LIB_XPM, and obtain it somehow.
2) fix the errors in bitmap.h by replacing _72 by 72 everywhere.
3) wait until Arun puts the fix I will mail him into the git repository.

The error in xboard.c is also in a conditionally compiled piece of code (also dependend on HAVE_LIBXPM) that Arun probably does not compile. There is a spurious [i] there that needs to be removed.

Re: xboard gtk

PostPosted: 09 Sep 2009, 11:42
by bodiless
Thank you!

OK I managed to get it to run although I am not sure it has been installed properly.

I am on a debian system and after make and make install I got two executables. One in /usr/local/bin/xboard, which is normal I guess, and one in the folder where all the installation files were. The first one is not working, it returns:

Code: Select all
Error: gtk_builder didn't work!
...
(xboard:4286): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion `GTK_IS_WIDGET (widget)' failed
...


But the second one, the one created in the installations files folder (:~/Desktop/xboard-gtk) is working.

OK mission accomplished. I had a glance at the new version but as I see it it still need some work. I wish I could help. Basically I wanted to see how the new ics input text would look like because on a linux system its impossible to chat or enter text decently. One need to type in the same text again and again, which is quite a pain. But this is not implemented yet, so I'll wait.

Thanks anyway.