Created attachment 337530 [details]
Patched ebuild - properly handling non-x86 arches.
After minor patching, the dev-util/qtcreator builds and runs smoothly on ~arm.
It requires patching the 3rdparty included botan tree to ensure that the cryptographic library works on non-x86 hardware - the problem should have been fixed by the upstream, however, in the meantime, the patch works.
It should work on all Little Endian non-x86 architectures.
Created attachment 337532 [details, diff]
And the actual qt-creator patch.
I guess the patch is already included in the upstream repo?
I don't think the patch in included in the upstream.. (actually finding the qt-creator upstream.. is a good question)
I just wrote it for my own use, hopefully it can be useful for someone else too.
Please send your patch upstream then.
(In reply to comment #4)
> Please send your patch upstream then.
No, to submit patches you MUST use https://codereview.qt-project.org/
I'd prefer if they provided a way to use system botan though...
(In reply to comment #5)
> (In reply to comment #4)
> > Please send your patch upstream then.
> > https://bugreports.qt-project.org
> No, to submit patches you MUST use https://codereview.qt-project.org/
> I'd prefer if they provided a way to use system botan though...
What's the point of the existing bug-tracking system then? :/
Does =dev-libs/botan-1.10* work on arm? If so, we should keyword it and force the usage of system botan on arm instead of patching qt-creator's internal copy.
>=qt-creator-2.7.0_rc always uses the system botan library (already keyworded on arm), therefore no patching is necessary anymore.
@arm: please verify that it works and add ~arm keyword.
Can not test it on arm, because of bug 460886
Added ~arm to dev-qt/qtdemo-4.8.4 cause it's dependency of dev-qt/qt-creator
Little note: trying to call Help from main menu(or calling Examples) lead to Segmentation fault. Other things seems to be OK.
+ 08 Apr 2013; Sergey Popov <firstname.lastname@example.org> qt-creator-2.7.0.ebuild:
+ Add ~arm keyword, wrt bug #454916