> Additional infos. I've (locally) modified relational.c
as follows:
>
> - add #include "util.h" in relational.c
> - replace PKGDATADIR with BuildFilename(NULL)
on line 83 ni
> relational .c
>
> Now it compiles but running says:
>
> Python supported.
> External players supported.
> XML match equity files supported.
> External commands supported.
> Windows sound system supported.
> SSE supported and available.
> (No game) relational test
> File "<string>", line 1
> relational('D:\Documents\Max\gnubg 0.16 noglade\', 'C:\Documents
> and Setting
> s\mmaini\.gnubg\')
>
^
> I’m not a python guy but in Python I am pretty
sure that \ is an
> escape character like c/c++ . I am wondering if that is the reason
> for this error?
Not sure, but not being an expert neither ...
> Out of curiousity under windows – What environment do you build
> with. Ming, MSVC, cygwin?
Mingw.
> I did a MING build of the Win GUI last
> night and didn’t see this issue with test (Although I was using
> Python2.5).
I'm using 2.5 too.
> I did find one bug relating to windows and the
new sound
> option screen (Where you choose files for each sound). Under windows
> the path separators are \ instead of unix where they are /. If you
> go into the sound screen make a minor change and then save settings
> you’ll get a “sound file not found” type error. This was a minor
fix
> in the sound code (Changing separator).
I think that the \ vs / issue can be solved (and is
mostly solved in gnubg) with proper coding. Fact is that conding cross-platform
is a bit of a pain and sometimes bugs like this just slip in.
> I too tried my first windows build in eons because of Hugh’s inquiry
;-).
I know, but I had some hard time recompiling with
python 2.5 (necessary) and, most important, I have a 1-month old little monster
that really sucks up all my sleep time: because of that, at the
office, as soon as I have 5 minutes, instead of building gnubg, I take a nap now
:)