On Thu, Mar 7, 2013 at 10:59 AM, Thomas Sachau <to...@gentoo.org> wrote: > Alexis Ballier schrieb: >> On Mon, 04 Mar 2013 21:17:50 +0100 >> Thomas Sachau <to...@gentoo.org> wrote: >>> dev-db/mysql abiwrapper >>> dev-lang/perl abiwrapper >>> dev-lang/python abiwrapper >>> dev-lang/ruby abiwrapper >>> dev-libs/gobject-introspection abiwrapper >>> dev-libs/libIDL abiwrapper >>> dev-scheme/guile abiwrapper >>> net-libs/courier-authlib abiwrapper >>> dev-qt/qtcore abiwrapper >>> dev-qt/qtgui abiwrapper >>> media-libs/fontconfig abiwrapper >>> www-servers/apache abiwrapper >>> x11-libs/pango abiwrapper >>> x11-libs/gtk+ abiwrapper >> >> >> Since you are doing this per-package and not per-binary: Do you happen >> to remember/have a list of the binaries that have abi-specific output? >> >> Also, for the qmake example, do you have an example of difference >> between qmake32 and qmake64? >> >> Alexis. >> > > I dont have a list of binaries, i either noticed myself some > abi-specific behaviour or got user reports for abi-specific behaviour. > As an example i remember, dev-libs/libIDL has a config binary not > matching the usual *-config scheme (libIDL-config-2), so instead of > adding a random list of patterns, i simply added that package to the > list of packages with wrapped binaries. The same applies to mysql, which > has a mysql_config binary. > > I am not sure about the target of your qmake question, so as a general > answer: > > qmake is something like configure for qmake based build systems. If you > want to see the difference between qmake (32bit) and qmake (64bit), run > a 64bit qmake on a qmake based package and do the same with a 32bit > qmake and check the difference between the 2 runs. >
Isn't this solvable by passing the right mkspec to a 64-bit qmake? Thanks, Pesa
