1 |
>>>>> On Sun, 25 Aug 2013, Thomas Sachau wrote: |
2 |
|
3 |
> workaround: add a variable, which changes the return of the function |
4 |
> checking for the current ABI (always true with variable, without |
5 |
> only true, when $ABI == $DEFAULT_ABI) |
6 |
|
7 |
Would this variable be set by the user, in profiles, or in ebuilds? |
8 |
|
9 |
> first version (multilib1.patch) directly changes the output of the |
10 |
> currently used multilib_is_native_abi() function: |
11 |
|
12 |
I think this would be very misleading. If a function is called |
13 |
multilib_is_native_abi then it should test for exactly that, not for |
14 |
something else. |
15 |
|
16 |
> second version (multilib2.patch) creates a new function, which |
17 |
> should then be used by ebuild authors to check, if they should build |
18 |
> ABI-specific content or not (using build_binaries() function instead |
19 |
> of multilib_is_native_abi() function) |
20 |
|
21 |
+build_binaries() { |
22 |
|
23 |
Name space pollution? Prefix with "multilib" please. |
24 |
|
25 |
+ if [[ ${COMPLETE_MULTILIB} == yes ]] ; then |
26 |
+ return 0 |
27 |
+ else |
28 |
+ multilib_is_native_abi |
29 |
+ fi |
30 |
|
31 |
This can be expressed much shorter (and clearer): |
32 |
|
33 |
[[ ${COMPLETE_MULTILIB} == yes ]] || multilib_is_native_abi |
34 |
|
35 |
But allow me a stupid question, why do you want to build binaries for |
36 |
other ABIs anyway? It's called multilib, not multibin. |
37 |
|
38 |
Ulrich |