On Sat, Oct 03, 2015 at 01:10:18PM +0200, Felix Fietkau wrote: > > As far as I understood this, libnl-tiny is a drop-in replacement for > > libnl-core. Or is there a difference in functionality or API/ABI? > libnl-tiny replaces the most commonly used parts of libnl-core + -genl. > The API is a bit more limited, but compatible for most applications. > The ABI is different, but that doesn't matter much. > > Any package that can easily work with libnl-tiny instead of libnl should > be changed to make use of it, since libnl-tiny is usually part of the > default package set. > > > Is it possible for instance to depend on libnl-tiny and libnl-route? > > (instead of libnl-core and libnl-route) > Mixing libnl based libraries with libnl-tiny does not work.
Thanks for the information. I've drafted some documentation based on this, feel free to improve: http://wiki.openwrt.org/doc/techref/libnl Baptiste
pgpNqnXGTFCnW.pgp
Description: PGP signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
