-
Notifications
You must be signed in to change notification settings - Fork 546
pkg-config support #299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Example file:
Or, if it's feasible to change installation layout, this way
|
So is there a convention used on UN*Xes to deal with cross-building (which includes building for 32-bit on 64-bit and building for 64-bit on 32-bit)? If so, the same convention should probably be used on Windows (there's nothing inherently special about Npcap here; that would apply to all libraries). |
On Unices binaries are installed to prefixes like |
Bump. Is there a decision if Npcap will integrate pkg-config support? If it will, shall directory layout be changed? How can I help besides providing libpcap.pc above? |
Thanks for the suggestion. So far we haven't received many requests for this, but this issue is a good place for people to comment if they are interested in pkg-config support for Npcap and why. Npcap OEM customers can also request it through their support channel and we will tally those requests as well. Also, does upstream libpcap support this? |
Upstream libpcap supports pkg-config from 1.9.0. |
"This" meaning what? Both autotools and CMake builds of libpcap will, if you do For an autotools file, it will be installed in
may be true of some UN*Xes but not all. On multi-architecture systems:
So the answer to "So is there a convention used on UN*Xes to deal with cross-building (which includes building for 32-bit on 64-bit and building for 64-bit on 32-bit)?" appears to be "No, there isn't a convention, there are several of them, and which one is used depends on the UN*X you're using." This means that Npcap isn't constrained by what various UN*Xes have done. It should do whatever works best in Windows build environments. The current installation layout for the SDK is
I don't know what issues modifying the installation layout to the proposed layout would cause for existing projects.
So where is the Windows pkg-config port, including the documentation where that's mentioned? |
Thanks a lot for enlightening, I stand corrected.
It's not a port, pkg-config upstream supports Windows.
Documentation for the mentioned feature: |
pkg-config tool can work on Windows and libpcap upstream has
libpcap.pc
. Can npcap SDK provide this file on Windows? It would eliminatelibpcap.a
/wpcap.lib
difference for cross-platform projects that use pkg-config, e.g. via meson build system.Probably 32-bit and 64-bit folder should have their own .pc files, so that they are selected by
PKG_CONFIG_PATH
.Prefix path can be set to some recommended location to install SDK, like
C:\Program Files\Npcap
.(Update: on Windows, pkg-config can detect prefix if file is placed inside
${prefix}/lib/pkgconfig
.)The text was updated successfully, but these errors were encountered: