On 10/2/09 12:50, "Yang Tse" <yangs...@gmail.com> wrote: >> I poked around the source tree and noticed that cURL does not even try to >> link against iconv unless you manually configure it like that (even though >> 99% of the time it's going to be in C library anyway.) Why is this? > > Not to GPL infect default configuration perhaps?
Oh, I see. But it seems like libiconv is LGPL licensed. Is that still bad? I've never looked at the source code before, so I could theoretically do a cleanroom utf-8 -> utf-16 conversion function and BSD license it.. -Josh ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
