summaryrefslogtreecommitdiff
path: root/check/gtk/kbproto.pc
diff options
context:
space:
mode:
authorDan Nicholson <dbn.lists@gmail.com>2012-11-21 10:50:17 -0800
committerDan Nicholson <dbn.lists@gmail.com>2012-11-28 05:59:49 -0800
commit160177d8d26c536dc085f938eadc8a43d9f2df29 (patch)
tree1916eb13931f3fad4229ad4b1139ed79d6ccf6f4 /check/gtk/kbproto.pc
parentf5b93bf1b18002c6409c8762d283e216fc045f5c (diff)
downloadpkg-config-160177d8d26c536dc085f938eadc8a43d9f2df29.tar.gz
Add a gtk testcase to provide something with complex interactions
The pkg-config testsuite has pretty good coverage of the implementation, but it lacks a complex case that tests the interactions of non-trivial .pc files. gtk is a very common package that meets this goal. This is a snapshot from my F16 system, and it should provide a good way to see how changes in the implementation regress a real world case.
Diffstat (limited to 'check/gtk/kbproto.pc')
-rw-r--r--check/gtk/kbproto.pc9
1 files changed, 9 insertions, 0 deletions
diff --git a/check/gtk/kbproto.pc b/check/gtk/kbproto.pc
new file mode 100644
index 0000000..9de27cd
--- /dev/null
+++ b/check/gtk/kbproto.pc
@@ -0,0 +1,9 @@
+prefix=/gtk
+exec_prefix=${prefix}
+libdir=${exec_prefix}/lib
+includedir=${prefix}/include
+
+Name: KBProto
+Description: KB extension headers
+Version: 1.0.5
+Cflags: -I${includedir}