| 1 |
On Fri, 8 Mar 2013 05:47:23 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> On Thu, 07 Mar 2013 19:59:35 +0100 |
| 5 |
> Thomas Sachau <tommy@g.o> wrote: |
| 6 |
> |
| 7 |
> > I am not sure about the target of your qmake question, so as a |
| 8 |
> > general answer: |
| 9 |
> > |
| 10 |
> > qmake is something like configure for qmake based build systems. If |
| 11 |
> > you want to see the difference between qmake (32bit) and qmake |
| 12 |
> > (64bit), run a 64bit qmake on a qmake based package and do the same |
| 13 |
> > with a 32bit qmake and check the difference between the 2 runs. |
| 14 |
> |
| 15 |
> Did you try to work with our Qt maintainers to find a solution? Or did |
| 16 |
> you just wrap it the Fedora way of solving things? |
| 17 |
|
| 18 |
You cannot blame him for that since the main idea behind |
| 19 |
multilib-portage is to be transparent for ebuild developers while |
| 20 |
portage will do all the multilib magic behind our back :) This approach |
| 21 |
has its pros and cons. |
| 22 |
|
| 23 |
A. |
Archives