[XBoard-devel] Fwd: C89/C99/ANSI compliance - cleanups needed?

[Joshua Pettus]

Begin forwarded message:

From: Joshua Pettus <address@hidden>

Subject: Re: [XBoard-devel] C89/C99/ANSI compliance - cleanups needed?

Date: January 12, 2016 at 8:25:34 AM EST

To: "H.G. Muller" <address@hidden>

I use to use to use winboard on wine with OSX to run windows engines, as part of a wineskin environment.  Now I’ve been running the engines directly with wine when I call them with OSX xboard, which is a lot simpler for me.  The mingw dev environment should be installed when installing the mingw compiler, else the compiler is useless for any other project as well.    I don’t think it needs to be included with winboard.

For the record, I use this script to set it up mingw with macports’ gcc on OSX.

install_mingw.sh
Description: Binary data

I’m sure it can be modified to work with apt-get or yum,  although the linux tools may already have a working mingw setup already.

Josh

On Jan 12, 2016, at 2:47 AM, H.G. Muller <address@hidden> wrote:

I think WinBoard should run under wine; I vaguely recall some people were doing that, and I did not receive any complaints.
I know some people are making MinGW cross compiles on Linux for their engine. Their binaries only work if you then also
install a 6MB DLL that is the MinGW cross compile of libc, however, and I don't consider it a viable option to put that in
the binary WinBoard distribution. But for testing if you have broken the WinBoard build it seems fine.

Op 1/12/2016 om 3:57 AM schreef Tim Mann:

does cross-compiling the code using mingw work, ie. building windows executables on linux that could be tested in wine?

I think that should work, but I haven't tried running WinBoard in wine for ages, and I don't think I ever tried cross-compiling for mingw from Linux.