protobuf/protobuf.pc.in

prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@

Name: Protocol Buffers
Description: Google's Data Interchange Format
Version: @VERSION@
Libs: -L${libdir} -lprotobuf @PTHREAD_LIBS@
Libs.private: @LIBS@

Cflags: -I${includedir} @PTHREAD_CFLAGS@
Conflicts: protobuf-lite
Allow dependents to use pkg-config to figure out what flags to pass to link against protobuf. 2009-08-03 21:31:25 +00:00			`prefix=@prefix@`
			`exec_prefix=@exec_prefix@`
			`libdir=@libdir@`
			`includedir=@includedir@`

			`Name: Protocol Buffers`
			`Description: Google's Data Interchange Format`
			`Version: @VERSION@`
`Libs` should not include `@PTHREAD_CFLAGS@` That should be only on the CFlags. When using the compiler as the linker driver, one may want to also call pkg-config to get the cflags, but when invoking the linker, there should be no compiler flags. 2019-01-04 21:08:21 +00:00			`Libs: -L${libdir} -lprotobuf @PTHREAD_LIBS@`
-lz in protobuf.pc belongs in Libs.private, not Libs 2012-07-03 09:52:54 +00:00			`Libs.private: @LIBS@`
Down integrate to GitHub 2019-06-11 23:00:16 +00:00
Revert "protobuf.pc.in does not reflect CXXFLAGS" This reverts commit a7180caf19ae150d9a3f9724600b0eed4b5da830. 2019-05-01 00:35:36 +00:00			`Cflags: -I${includedir} @PTHREAD_CFLAGS@`
Uncomment conflict fields from pkg-config files. The referenced bug was fixed in 2007 and has been released in pkg-config-0.23 (16.Jan.2008). The fixed version is widely available. 2015-05-12 15:50:05 +00:00			`Conflicts: protobuf-lite`