On Wed, Oct 22, 2014 at 16:07, Michael B. Trausch wrote: > I have done a very ugly port that builds and works in the few > scenarios that I've tested with, but it's not complete as some > features (mostly the ones that allow disabling at compile time) need > more work to finish porting.
I think the first piece is of course the necessary build files. Access to Windows machines isn't really a problem, so sorting out the necessary ifdefs or other changes can be done on a case by case basis, but first we need the infrastructure in place to start feeding everything into the compiler. It sounds like you already have this. Makefiles? Posting those files somewhere would be a great start, and since it's entirely independent of existing code it can be integrated fairly easily even if it doesn't build without further changes. The portable libressl releases have tried to push the compatibility changes out of the main sources, confining them to isolated platform specific files, but I recognize that the Windows changes may be more extensive. I think our strategy will be to include some minor ifdefs where necessary, or to copy files in other cases. i.e., socket.c may become winsocket.c. We're trying to avoid too much interleaving within individual files.
