1 |
On Thu, 07 Mar 2013 19:59:35 +0100 |
2 |
Thomas Sachau <tommy@g.o> wrote: |
3 |
> |
4 |
> I dont have a list of binaries, i either noticed myself some |
5 |
> abi-specific behaviour or got user reports for abi-specific behaviour. |
6 |
> As an example i remember, dev-libs/libIDL has a config binary not |
7 |
> matching the usual *-config scheme (libIDL-config-2), so instead of |
8 |
> adding a random list of patterns, i simply added that package to the |
9 |
> list of packages with wrapped binaries. The same applies to mysql, |
10 |
> which has a mysql_config binary. |
11 |
|
12 |
Ok, so those make perfect sense for being wrapped and should be done |
13 |
per-binary not per-package: We do not really want to wrap all mysql |
14 |
binaries just for mysql_config. |
15 |
Ebuilds should declare the binaries they want to be wrapped, so we can |
16 |
grep the tree for getting a list of what to fight against if we want a |
17 |
cleaner multilib system :) |
18 |
|
19 |
> I am not sure about the target of your qmake question, so as a general |
20 |
> answer: |
21 |
> |
22 |
> qmake is something like configure for qmake based build systems. If |
23 |
> you want to see the difference between qmake (32bit) and qmake |
24 |
> (64bit), run a 64bit qmake on a qmake based package and do the same |
25 |
> with a 32bit qmake and check the difference between the 2 runs. |
26 |
|
27 |
Well, I'm asking this because I don't have access to a 32bit qmake |
28 |
here so a diff of the files generated by the two will be useful :P And I |
29 |
believe it makes sense to study in details this case to understand |
30 |
whether we want to wrap it or not. As Davide said, it is likely that |
31 |
overriding the correct variable may make qmake output not abi-specific. |
32 |
The difference between g++-64 and g++-32 qmake mkspec is only a -m32 vs |
33 |
-m64 cflag which I think is overridden elsewhere in our ebuilds so this |
34 |
should not matter much. |
35 |
|
36 |
Alexis. |