Blame lib/libqb.pc.in

Packit Service f88c7f
prefix=@prefix@
Packit Service f88c7f
exec_prefix=${prefix}
Packit Service f88c7f
libdir=@libdir@
Packit Service f88c7f
includedir=${prefix}/include
Packit Service f88c7f
Packit Service f88c7f
Name: libqb
Packit Service f88c7f
Version: @PACKAGE_VERSION@
Packit Service f88c7f
Description: libqb
Packit Service f88c7f
Requires:
Packit Service f88c7f
Libs: -L${libdir} -lqb @client_dlopen_LIBS@
Packit Service f88c7f
# NOTE: If -lqb not usable for linking (e.g. linker not compatible with
Packit Service f88c7f
#       linker scripts ad-hoc modifying output sections), try recent
Packit Service f88c7f
#       ld.bfd/binutils linker first when available, otherwise you can
Packit Service f88c7f
#       try "-l:libqb.so.<digit>" link switch that bypasses said linker
Packit Service f88c7f
#       script -- but beware, logging may be less efficient and may lack
Packit Service f88c7f
#       possible future optimizations and extra features.  Consequently,
Packit Service f88c7f
#       logging issues (typically bound to QB_LOG_INIT_DATA macro) can be
Packit Service f88c7f
#       mitigated with QB_KILL_ATTRIBUTE_SECTION macro defined for a build.
Packit Service f88c7f
# NOTE: when concerned about a warning coming from the build process like
Packit Service f88c7f
#       warning: [...]libqb.so contains output sections; did you forget -T?
Packit Service f88c7f
#       and the build finishes OK, take it merely as a harmless side-effect
Packit Service f88c7f
Libs.private: @LIBS@
Packit Service f88c7f
Cflags: -I${includedir}