summaryrefslogtreecommitdiffstats
path: root/libnl-3.0.pc.in
Commit message (Collapse)AuthorAgeFilesLines
* build: add Libs.private field in libnl pkg-config fileFabrice Fontaine2022-03-101-0/+1
| | | | | | | | | | | | | | | | | | In order to support static linking, the libnl pkg-config file should indicate in its Libs.private field the libraries that libnl-3.0.a requires. The LIBS variable contains the appropriate list of libraries: -lm in all cases, and -lpthread when pthread support is enabled. This allows to statically link applications against libnl properly. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> [Retrieved from: https://git.buildroot.net/buildroot/tree/package/libnl/0001-build-add-Libs.private-field-in-libnl-pkg-config-fil.patch] Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [thaller@redhat.com: btw, "-lm" is not used anymore] https://github.com/thom311/libnl/pull/229
* Switch to libtool versioning systemThomas Graf2011-09-131-0/+10
| | | | | | | | | | | | | | | | | | It has been a request that multiple libnl versions should be installabe in parallel. In order to achieve this, the basename of the library was changed to libnl-3 which reflects the 3rd generation of libnl APIs. It also means that release based library versioning is left behind and libtool versioning is used instead. Projects using pkgconfig will automatically link against the new library basename and will not notice a difference. The SO versioning is based on the glib model: current := 100 * minor + micro - revision revision := revision age := age (number of backwards compatible versions)
* 3.1 releaseThomas Graf2011-08-111-10/+0
|
* libnl-3.0libnl3_0Thomas Graf2011-03-211-0/+10