1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 28/11/12 08:26 PM, Richard Yao wrote: |
5 |
> On 11/28/2012 05:21 PM, Michał Górny wrote: |
6 |
>> On Wed, 28 Nov 2012 22:49:14 +0100 Justin <jlec@g.o> |
7 |
>> wrote: |
8 |
>> |
9 |
>>> Hi, |
10 |
>>> |
11 |
>>> and another one. |
12 |
>>> |
13 |
>>> Problem: Some packages aren't lucky and their buildsystem |
14 |
>>> doesn't create pkg-config files out of the box. |
15 |
>>> |
16 |
>>> Solution: Create them by hand. |
17 |
>> |
18 |
>> Result: packages which fail to build on distributions other than |
19 |
>> Gentoo because their authors were using Gentoo and didn't knew |
20 |
>> that the pkg-config aren't anywhere else. |
21 |
>> |
22 |
> |
23 |
> I suspect that the .pc files would probably be available if people |
24 |
> installed -dev packages. If not, people can blame the distribution |
25 |
> developers for breaking things. |
26 |
> |
27 |
|
28 |
They wouldn't be if upstream doesn't provide them and only Gentoo did, |
29 |
which is what this eclass would be for.. Standard rules of |
30 |
development, if the lib doesn't provide a .pc file then you can't use |
31 |
pkg-config to configure your software for it. There's no point in |
32 |
providing a .pc file if nothing is going to use it, and we (gentoo |
33 |
developers) definitely do not want to end up patching and maintaining |
34 |
patches on both a lib and all its rdeps just so that it support pkgconfig. |
35 |
|
36 |
(i came across this situation already and learned a bit the hard way |
37 |
with spidermonkey. It sucked to have to use checks for filenames and |
38 |
special defines in header files to find the right libs, but that was |
39 |
still the only "right" way to do it until spidermonkey upstream |
40 |
finally started bundling a .pc) |
41 |
|
42 |
-----BEGIN PGP SIGNATURE----- |
43 |
Version: GnuPG v2.0.19 (GNU/Linux) |
44 |
|
45 |
iF4EAREIAAYFAlC3ZLkACgkQ2ugaI38ACPANHAD/RtWy8/K6U58PQWvk7CyfRSth |
46 |
1WrlSwbjJslioWfaRvYA/RMnJX9/Js1YkYHZBGHk28dK2GzwrxJh872MqsCqWEVR |
47 |
=4EwJ |
48 |
-----END PGP SIGNATURE----- |