15.03.2013, 12:36, "Nils Durner" <[email protected]>:
Hello everybody,
> Sadly, can't do anything about PlibC SVN, you'd have to ask ndurner,
> if he ever comes out of coma. That just happened, LRN now has developer access on SF.
Nice and unexpected!
Is it OK to continue PlibC discussion here?
Is it OK to continue PlibC discussion here?
15.03.2013, 11:04, "LRN" <[email protected]>:
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.
LRN, my first commit is your UTF-8 patch with some fixes.
As you can update SVN now, I hope this will happen soon. :) Right now people are using plibc source with your patch with my fixes to build mircohttpd. Like on https://aur.archlinux.org/packages/mingw-w64-plibc/
With my patches it possible to compile PlibC on MinGW32, MinGW-w64 win32 and MinGW-w64 win64.
I also introduced one api breaking change (need to specify buffer size when calling lib function with app-allocated buffer), but seems that noone is using this function.
As you can update SVN now, I hope this will happen soon. :) Right now people are using plibc source with your patch with my fixes to build mircohttpd. Like on https://aur.archlinux.org/packages/mingw-w64-plibc/
With my patches it possible to compile PlibC on MinGW32, MinGW-w64 win32 and MinGW-w64 win64.
I also introduced one api breaking change (need to specify buffer size when calling lib function with app-allocated buffer), but seems that noone is using this function.
If code is mostly OK for you, I'll improve it furthermore, to use real buffer checking inside PlibC and use windows native softlinks.
Best Wishes,
Evgeny
