|
From: | H.G. Muller |
Subject: | Re: [XBoard-devel] C89/C99/ANSI compliance - cleanups needed? |
Date: | Mon, 11 Jan 2016 22:32:52 +0100 |
User-agent: | Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 |
But it should not be that difficult for you to test if WinBoard would still compile, (as opposed to link). If you can compile *.c in the winboard directory with "gcc -c" and the *.c files in the base directory with "gcc -c -DWIN32", and don't move any code from the shared backend files to the XBoard front-end (e.g. from engineoutput.c to nengineoutput.c) it should be more or less OK. The only problem could be a few Windows-specific headers, like windows.h, but I am sure we could sent these to you (e.g. from Cygwin, which I use to build WinBoard) so that you can put them on your
system together with the other includes. H.G. Op 1/11/2016 om 9:58 PM schreef Thomas Adam:
On 29 March 2015 at 18:34, Arun Persaud <address@hidden> wrote:Hi Sounds like a good plan, we can always need more people to help with the code base and cleaning up the code a bit would be great.So... almost a year later... whoops. I'm still here---the reason I've not done anything development-wise, is I'm finding having the windows port in XBoard a hindrance, so I've no way of testing if my changes work/or break it. Plus, I think it unacceptable to leave that to those who can look at this, to fix things. Can anyone advise on the best course of action? -- Thomas Adam
[Prev in Thread] | Current Thread | [Next in Thread] |