blob: a81c6d704a28eec8372d323daeac4d201829b0ae (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 16/11/2011 10:44, Guillaume Rousse wrote:
<blockquote cite="mid:4EC38611.1040608@gmail.com" type="cite">Le
16/11/2011 00:11, jcc a écrit :
<br>
<blockquote type="cite">Hi,
<br>
<br>
I do not quite understand why with BuildRequires and Requires,
it is
<br>
sometimes necessary to place a pkgconfig(any_lib) instead of
simply
<br>
any_libin the spec file.
<br>
</blockquote>
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.
<br>
<br>
</blockquote>
<br>
<div style="width: 100%;"><br>
</div>
<div id="gt-res-content" class="almost_half_cell">
<div dir="ltr" style=""><span id="result_box" class="short_text"
lang="en"><span class="hps">I thank you for</span> <span
class="hps">these explanations.</span><br>
<br>
<span class="hps">Sincerely, J.-C.<br>
</span></span></div>
</div>
</body>
</html>
|
