What's the diffence between one platform api like aio and another like win32? They have about the same effect on our code. We can't distribute their libs and they don't force us to change our licensing terms.
Btw the compiler you use has nothing to do with the libs you link against. And most Linux apps link against glibc. It's just a platform API. Which the official apache policy says there are no problems on linking against. On Wednesday, December 23, 2015, Daniel Kulp <[email protected]> wrote: > > > On Dec 23, 2015, at 6:45 PM, Clebert Suconic <[email protected] > <javascript:;>> wrote: > > > > > > Anyways, Saying you can't depend on anything LGPL is the same as > > saying you can't depend on Linux or anything coming from Linux. for > > instance Apache HTTP (the very first project that founded this > > organization) would be breaking the apache license itself by using > > libc. (Open the source code if you don't believe me). > > > > It's certainly not the case...as libc is a platform API. > > Except you can build HTTP on Linux and NOT depend on the gnu license > libc. I can use clang as the compiler (or the intel compiler or ….) and > not end up with a dependency on a LGPL library. If you have a non-LGPL > version of libaio, then by all means, let’s use it. > > > libaio is also a platform API. > > libaio is NOT installed by default on pretty much any of the linux > “platforms" so I would have a hard time considering as a part of the > platform. > > > -- > Daniel Kulp > [email protected] <javascript:;> - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > > -- Hiram Chirino Engineering | Red Hat, Inc. [email protected] | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
