Okay, a bit of a deeper problem. I've successfully built it on OS X. If I run it with my old .xboardrc, it displays a blank board and complains that the old -pixmapDirectory and -bitmapDirectory arguments are no longer recognized. Fair enough, it's SVG now. So I provide "-pieceImageDirectory ./svg" (from the build root), and it crashes on startup with the error:
Assertion failed: (_cairo_status_is_error (status)), function _cairo_error, file cairo-error.c, line 68. It if helps, my version of cairo is 1.12.4. Cheers, Adrian On Sun, Oct 21, 2012 at 10:43 PM, Adrian Petrescu <[email protected]>wrote: > Okay, the problem seems to be that some gettext-tools (in this case, > msgfmt) weren't linked in properly. > > Never mind! > > On Sun, Oct 21, 2012 at 9:50 PM, Adrian Petrescu <[email protected]>wrote: > >> Hey xboard-devel! >> >> I'm trying to build this latest dev release from master (super-excited >> about SVG), but I'm getting the following build error on OS X 10.8.2: >> >> make all-recursive >> Making all in po >> test ! -f ./xboard.pot || \ >> test -z "da.gmo de.gmo es.gmo it.gmo ru.gmo tr.gmo uk.gmo vi.gmo >> zh_CN.gmo zh_HK.gmo zh_TW.gmo" || make da.gmo de.gmo es.gmo it.gmo ru.gmo >> tr.gmo uk.gmo vi.gmo zh_CN.gmo zh_HK.gmo zh_TW.gmo >> rm -f de.gmo && : -c --statistics --verbose -o de.gmo de.po >> rm -f da.gmo && : -c --statistics --verbose -o da.gmo da.po >> rm -f es.gmo && : -c --statistics --verbose -o es.gmo es.po >> rm -f it.gmo && : -c --statistics --verbose -o it.gmo it.po >> rm -f ru.gmo && : -c --statistics --verbose -o ru.gmo ru.po >> rm -f tr.gmo && : -c --statistics --verbose -o tr.gmo tr.po >> rm -f vi.gmo && : -c --statistics --verbose -o vi.gmo vi.po >> rm -f uk.gmo && : -c --statistics --verbose -o uk.gmo uk.po >> mv: rename t-it.gmo to it.gmo: No such file or directory >> mv: rename t-de.gmo to de.gmo: No such file or directory >> mv: rename t-es.gmo to es.gmo: No such file or directory >> mv: rename t-da.gmo to da.gmo: No such file or directory >> mv: rename t-ru.gmo to ru.gmo: No such file or directory >> make[3]: *** [it.gmo] Error 1 >> make[3]: *** Waiting for unfinished jobs.... >> make[3]: *** [de.gmo] Error 1 >> make[3]: *** [da.gmo] Error 1 >> mv: rename t-tr.gmo to tr.gmo: No such file or directory >> make[3]: *** [es.gmo] Error 1 >> make[3]: *** [ru.gmo] Error 1 >> mv: rename t-vi.gmo to vi.gmo: No such file or directory >> make[3]: *** [tr.gmo] Error 1 >> make[3]: *** [vi.gmo] Error 1 >> mv: rename t-uk.gmo to uk.gmo: No such file or directory >> make[3]: *** [uk.gmo] Error 1 >> make[2]: *** [stamp-po] Error 2 >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 >> >> (I used to be able to build in this environment with no problem). >> >> Any idea what I might be doing wrong? Let me know if there's any other >> details about my build environment you need! >> >> Cheers, >> Adrian >> >> On Sun, Oct 21, 2012 at 5:00 PM, Arun Persaud <[email protected]> wrote: >> >>> Hi >>> >>> there is a new developer release available with some bigger changes. We >>> now use cairo for most or all of the drawing and SVGs for the pieces. >>> This allowed for example to make the XBoard main window resizable ;) >>> >>> Try it out and let us know how its working for you and what we can/need >>> improve on! It would also be great to know if the configure scripts >>> works on all operating systems. >>> >>> The next item on the list is doing the GTK port (again). You can already >>> try it out in HGM's git tree if you want. Due to lot of restructuring >>> lately we now are in a position of only having Xt calls in a very small >>> amount of files and are just porting those. In the end we want to have >>> Xt and Gtk in parallel available (via configure --with-gtk or something >>> like that) and perhaps also get a native OS X front-end and perhaps >>> update the native windows one. >>> >>> We were also thinking about adding some kind of theme-support, which >>> will probably come after the gtk port. More or less it will let you >>> choose which svg directory you want to use together with some other >>> items such as background texture for the board and colors. The >>> mono-option will then just be a mono-theme for example. >>> >>> HGM can probably give a more detailed update, since I was only involved >>> in some configure questions, SVGs and other very minor details. >>> >>> cheers >>> ARUN >>> >>> >> >
