summaryrefslogtreecommitdiff
path: root/libpcap.pc.in
Commit message (Collapse)AuthorAgeFilesLines
* autoconf, cmake: fix generated pcap-config and libpcap.pc.Guy Harris2022-09-271-1/+2
| | | | | | | | | | | | | | | | | | | | | In libpcap.pc, don't put libraries into Libs.private if we can just put the package to which the libraries belong in Requires.private and let pkg-config do the work. When configuring with CMake, make sure that we do *NOT* put library full paths into the lists of libraries required when linking statically against libpcap. In the configure script, do a push settings/pop settings operation before checking various libraries similar to what's done in CMake files, to make sure that the results of the tests aren't affected by tests done previously. Have the macros for autoconf that run pcap-config take arbitrary arguments rather than a single flag value, to allow testing with --libs and --static. This should fix issue #1062.
* autotools, cmake: provide an rpath option if necessary.Guy Harris2022-09-261-1/+1
| | | | | | | | | On platforms where a program built with a libpcap installed somewhere other than the default system library directory must be linked with an rpath option to cause the program to, when run, find the library with which it was linked, specify that flag in the output from pcap-config and the output produced by pkg-config when used with our libpcap.pc file.
* Add a pkg-config .pc file for libpcap.Guy Harris2018-04-251-0/+18
Addresses GitHub issue #374.