| 1 |
On Wed, 23 Jan 2013 09:24:26 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> On Mon, 21 Jan 2013 10:27:30 -0300 |
| 5 |
> Alexis Ballier <aballier@g.o> wrote: |
| 6 |
> |
| 7 |
> > > To be honest, I don't know if there's other way to hide USE flags |
| 8 |
> > > than using USE_EXPAND_HIDDEN. If we want to use that, we'd have |
| 9 |
> > > to split the flags per-arch, i.e. have: |
| 10 |
> > > |
| 11 |
> > > MULTILIB_AMD64="abi1 abi2 abi3" |
| 12 |
> > > MULTILIB_PPC64="abi1 abi2 abi3" |
| 13 |
> > > |
| 14 |
> > > with appropriate USE_EXPAND_HIDDEN set by profiles. |
| 15 |
> > |
| 16 |
> > I don't like that at all. |
| 17 |
> > I'd go for ABI= the union of all the MULTILIB_ABIS variables (if |
| 18 |
> > there is no name collision) |
| 19 |
> > we certainly want skype to depend on libitneeds[abi_x86], not |
| 20 |
> > 'amd64? ( libitneeds[abi_amd64_x86] ) x86? ( libitneeds )' |
| 21 |
> |
| 22 |
> Just a quick idea. |
| 23 |
> |
| 24 |
> How would you feel about abi_x86_32? (similarly _64, _x32) |
| 25 |
> |
| 26 |
> That would be almost natural names with the trick variable being |
| 27 |
> ABI_X86, therefore having all the fore-mentioned advantages. |
| 28 |
> |
| 29 |
> The deps would look like: |
| 30 |
> |
| 31 |
> libitneeds[abi_x86_32] |
| 32 |
> |
| 33 |
|
| 34 |
Sounds good too, I just would want it to be shared between arches that |
| 35 |
can: amd64/x86/x32, ppc/ppc64, mips, sparc32/sparc64, etc. |
| 36 |
You mean you will hide ABI_X86 USE_EXPAND on non-x86 arches, right ? |
| 37 |
This would have all the benefits I think, very good idea :) |
| 38 |
|
| 39 |
Alexis. |
Archives