In order to build winboard properly, we must #include the correct
config.h file from the winboard directory.
If this file happens to be present in the xboard directory, all the
cmdline compilers I'm testing will #include the wrong one. I suspect
the GUI ones won't suffer from this problem, but I'm not sure yet. This
problem affects devs more than regular users, since we are more likely
to actually have config.h in the xboard directory.
So what do we do?
1) nothing. Assume the devs are smart enough to just delete the
config.h from the xboard directory when this happens. When we package
the source, there shouldn't be a config.h in the xboard directory
anyway, so end users trying to compile winboard should never get this
problem.
2) update the GCC and MS makefiles to remove ..\config.h. I don't see
any immediate downside to this, but it seems kludgy.
3) rename winboard/config.h to something else. I'm not sure what
ramifications this might have. All the files in the xboard directory
that we need actually do need winboard/config.h. The problem is that
config.h in the xboard dir is automatically generated, while the one in
the winboard directory isn't. Maybe it used to be at one point, but it
became a sort of bastardized version of config.h specific to windows.
Unfortunately, it's the one we actually need right now.
4) other ideas?
