From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-November/009579.html | 73 ++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-November/009579.html (limited to 'zarb-ml/mageia-dev/2011-November/009579.html') diff --git a/zarb-ml/mageia-dev/2011-November/009579.html b/zarb-ml/mageia-dev/2011-November/009579.html new file mode 100644 index 000000000..0d59423f0 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009579.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] BuildRequires and pkgconfig + + + + + + + + + +

[Mageia-dev] BuildRequires and pkgconfig

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Wed Nov 16 10:44:49 CET 2011 +

+
+ +
Le 16/11/2011 00:11, jcc a écrit :
+> Hi,
+>
+> I do not quite understand why with BuildRequires and Requires, it is
+> sometimes necessary to place a pkgconfig(any_lib) instead of simply
+> any_libin the spec file.
+If you have a dependency for any_lib, you'll only get the runtime part 
+of the lib. If you need to build something with the lib, you'll need the 
+buildtime part of the lib, which is generally isolated in the -devel 
+package. Hence the need for a build dependency of either any_lib-devel 
+(always present), or pkgconfig(any_lib), which is a virtual package 
+automatically generated by rpm if a pkgconfig file is present.
+
+-- 
+BOFH excuse #442:
+
+Trojan horse ran out of hay
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1