On Jul 11, 2:42 pm, Henrik Schröder <[email protected]> wrote:
> I'm not so sure that mingw is the right way to get it working on windows,
> the stable versions you can find athttp://code.jellycan.com/memcached/were
> made to work in Visual Studio, which is the "standard" for making C programs
> on windows, like it or not. There's a free version of it
> here:http://www.microsoft.com/express/vc/
>
> Other than that, the main differences between windows and posix is
> networking and daemonizing. The windows port at jellycan contains helper
> libraries for that and has integrated them, you should definitely look at
> that if you haven't already.
I've looked at it, but the diff is one very large and coarse
change. It's not something that can be merged and is quite invasive.
My understanding (and I can't find anything to the contrary -- MS's
site is just awful an makes it quite difficult to find a simple
answer) is that VS doesn't support C99. The jellycan diff shows a few
areas where valid C99 code was modified for C89 compliance.
Supporting Windows is difficult and expensive, but there was one
very specific constraint that I'd placed on the porting effort to
ensure it would be acceptable and maintainable:
A new platform port must touch the existing code as absolutely
little as possible.
That's where it is now -- there's about 18 lines of diff in
memcached.c (and some of that is *removing* platform-specific
ifdefs). The rest of changes are found in a new directory with new
files that provide missing pieces or fit into the platform better.
Now, if VC actually *can* follow a 10-year-old standard to at least
some degree, it might be acceptable. As it is, I'd be happy to have
*anything* work, though.
I hope I don't sound too unwilling to compromise, but as it is we
can't get anyone to help support a porting effort, so putting more
onus on the existing development community, most of whom probably know
Windows about as well as I do, is unreasonable at this point.
Besides, we even killed off support for one of our beloved UNIX
platforms for lack of a C99 compiler. :)
> You should probably also look at how libevent
> has done it's windows-specific code, I think they have an active windows
> maintainer, might be a good idea to talk to that person as well?
Perhaps. This is a foreign land to me.
> I'm sorry I can't be of any more help, but I'll gladly cheer you on, I would
> love to see 1.4 on windows so I can start implementing the binary protocol
> in my client. :-)
Hey, you're free to do that anyway. Surely someone uses your client
with a non-Windows server. :)
