When linking dynamically, the shared library contains a reference to all external dependencies, and the linker can easily resolve them. However when linking statically, all external dependencies have to be specified explicitly. This rule also applies to dependencies that are not exposed through the public api. The pkg-config Requires.private field is used to support both static and dynamic linking correctly.
12 lines
300 B
PkgConfig
12 lines
300 B
PkgConfig
prefix=@prefix@
|
|
exec_prefix=@exec_prefix@
|
|
libdir=@libdir@
|
|
includedir=@includedir@
|
|
|
|
Name: libdivecomputer
|
|
Description: A library for communication with various dive computers.
|
|
Version: @VERSION@
|
|
Requires.private: @DEPENDENCIES@
|
|
Libs: -L${libdir} -ldivecomputer
|
|
Cflags: -I${includedir}/libdivecomputer
|