libmicrohttpd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libmicrohttpd] PlibC in microhttpd


From: LRN
Subject: Re: [libmicrohttpd] PlibC in microhttpd
Date: Fri, 15 Mar 2013 10:39:39 +0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Thunderbird/22.0a1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/14/2013 08:13 PM, Evgeny Grin wrote:
> microhttpd require PlibC version with UTF-8, which are hardly
> available on net. While this isn't a problem for Linux as
> microhttpd contains required header, but for Windows this is a real
> problem. As I need microhttpd for Windows (both x32 and x64), I
> started new PlibC branch with UTF-8 and fixes for Win64. It's
> available on as archive at 
> http://code.google.com/p/mingw64-further/downloads/list?q=Type%3DSource+PlibC
>  and on github: https://github.com/Karlson2k/PlibC. Is it worth to
> update header in microhttpd with new and fixed version of PlibC?
> 
Here's the conversation i had with ndurner about my patches to PlibC
that add utf-8 support for W32:

2011-12-27 15:50:17 LRN: ndurner, when will you have time to check
https://sourceforge.net/tracker/?func=detail&aid=3465706&group_id=137319&atid=738312
?
2011-12-27 16:59:29 ndurner: LRN: early next year
2011-12-27 17:00:00 LRN: "early" as in "January 1, 10 AM"? :)
2011-12-27 17:19:16 ndurner: hehe, no ;-)
2011-12-27 17:19:22 ndurner: End of January erliest

Yeah, it's been more than a year. He never reviewed the patch.
After a while it became obvious that this isn't going forward, so we
just said "to hell with it", and updated PlibC-dependent packages to
use my patched version, even though the patch was not accepted in
PlibC SVN.
You can fetch the patches i use (along with the buildscript) from [1].
Mostly it's the utf8ization patch, but also some fixes on top of it.

Now, i've looked at your github commits, and there a whole page of them.
Once i have some time, i'll try to review them and, if everything's
ok, use them myself.

Sadly, can't do anything about PlibC SVN, you'd have to ask ndurner,
if he ever comes out of coma.

That said, we may just fork PlibC on gitorious, forget about ndurner,
and call it a day. Or plead our case to sourceforge admins and get
commit access to PlibC SVN repository. Or just ask ndurner nicely.

[1]
https://www.gitorious.org/sbuild/sbuild/trees/master/src/mingw/libplibc-svn-r88-6

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRQsIQAAoJEOs4Jb6SI2CwbCkH/32tMGmg1TjD1m4fgjcbq7lr
axXauLHnwU1HGEyx3PcFcxVWqaOU2YKcVm6vtuLH2K5T42/aaoRtL4Kv2Uu9QkmP
0bx3Y7UpBiDNk8N6KFqThefDBXxcCXmhIL0W58HS0l/V6i0d/1UplBcbTw5oYUi3
Sh38CktZKGnnjhEeKiF/dKy5MjJgb/qTdDTZTJXFrKF0UJB4HoLGYkQh7+EFBEmE
X0TWWv9ASSlhuNhmtI+VhUWOlFBKIqAM8DW1gOX2dtomj3FI9VBwGldvi80EDyKz
CRFmDcyJXM/RvlKgKncmDaTQt5A3YAsPFwLYl6dqpGjAMw1i6pqm4gUM11clI3k=
=RjrD
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]