Tweaked qt ebuild [OBSOLETE]

Message

nxsty · Post by **nxsty** » Wed Jan 25, 2006 6:31 pm

This ebuild isn't maintained anymore, use the one from the xeffects overlay instead!

Tweaked qt-ebuild

I just migrated to KDE so I thought why not twek this thing to death too.

I modified the qt ebuild to build qt-copy instead of the official tarball. Qt-copy is a version of qt enhanced by the KDE devs with various fixes and optimizations. For ex. qt usually repaints a progressbar everytime it's updated but with qt-copy it only repains when necessary, and it also makes qt less dependant on slow fontconfig which should somewhat speed up the startup time for some apps. For more info about qt-copy check KDE SVN, especially the "patches" dir.

I also added a "risky" USE-flag that builds qt itself with visibility settings for even more space saving and performance. This breaks the ABI so it might be dangerous, hence the name, but it also might speed up qt quite a bit. Use at your own risk!! To enable symbol visibility for KDE, make sure you have gcc 4.1 or later and set the new "kdehiddenvisibility" USE-flag.

Set the pertty USE if you want the improving KDE/pertty patch.

The bug report about qt-copy is here, but the devs doesn't seem interested

:
http://bugs.gentoo.org/show_bug.cgi?id=120464

To use:
1. Download the overlay from http://snigel.no-ip.com/~nxsty/linux/qt-overlay.tar.bz2
2. Untar it in /usr/local/portage/x11-libs/
3. Edit make.conf and make sure you have PORTDIR_OVERLAY="/usr/local/portage"
4. Backup your old qt with quickpkg
5. emerge qt

For best performance you should also use fontconfig 2.4.1 available in ~arch.

Changelog:

2006-10-22
*Synced with portage.

2006-08-14
*Updated fontconfig to the 2.4 release.

2006-06-05
*New qt-copy snapshot.
*Synced with portage.
*Added a fc-cache speedup patch for fontconfig.

2006-03-27
*Updated to qt 3.3.6!

2006-02-03
*I updated my fontconfig overlay with a lot of fixes from upstream and suse. Everybody using it should upgrade!

2006-02-02
*New qt-copy snapshot.

2006-02-01
*Added the improving KDE/pertty patch controlled by a pertty USE-flag.

StringCheesian · Post by **StringCheesian** » Wed Jan 25, 2006 8:44 pm

Awesome! How come the "KDE related patches" are commented out? Would it be a bad idea for me to try them?

nxsty · Post by **nxsty** » Wed Jan 25, 2006 8:58 pm

StringCheesian wrote:Awesome! How come the "KDE related patches" are commented out? Would it be a bad idea for me to try them?

Some of them where already commented out and the others are included in qt-copy. You could try enabling them to see what happens but I guess most of them would reject.

jarealist · Post by **jarealist** » Thu Jan 26, 2006 3:12 am

Another nxsty gem! Noticeable improvement in KDE. Thanks again for all the good stuff.

StringCheesian · Post by **StringCheesian** » Thu Jan 26, 2006 3:48 am

KDE shuts down without kicker crashing! Thank you nxsty.

feld · Post by **feld** » Thu Jan 26, 2006 4:13 am

so you build this QT and then rebuild KDE? Or do you not have to rebuild KDE?

Just kinda confused how this optimized QT build interacts with KDE

-Feld

BTW, where'd your firefox overlay go? Did that get pushed into portage?

steveb · Post by **steveb** » Thu Jan 26, 2006 4:48 am

Let my try this thing with gcc 4.1.0 beta. Will post my results.

cheers

SteveB

enderandrew · Post by **enderandrew** » Thu Jan 26, 2006 7:22 am

I set this to compile with the latest gcc 4.1 snapshot as I was walking out the door on one of my machines. I also enabled the "risky" use flag.

nxsty · Post by **nxsty** » Thu Jan 26, 2006 9:11 am

feld wrote:so you build this QT and then rebuild KDE? Or do you not have to rebuild KDE?

Just kinda confused how this optimized QT build interacts with KDE

-Feld

BTW, where'd your firefox overlay go? Did that get pushed into portage?

You don't need to rebuild KDE to get the benefits from qt-copy, but you can rebuild it to enable symbol visibility but then the kde eclass needs some tweaking first. I'm going to write another post about that.

Yes, they're included in mozilla-firefox-1.5-r9.

no idea · Post by **no idea** » Thu Jan 26, 2006 11:05 am

What version of QT is it based on?

nxsty · Post by **nxsty** » Thu Jan 26, 2006 11:31 am

no idea wrote:What version of QT is it based on?

3.3.5

no4b · Post by **no4b** » Thu Jan 26, 2006 2:29 pm

naxty will create his own distribution in a short time

Thx for the ebuild. Btw. if it's so good, maybe fill the report on bugzilla and developers will add qt-copy patches to the official ebuild (for example available as USE flag). I used them on freebsd and there were no problems.

enderandrew · Post by **enderandrew** » Thu Jan 26, 2006 2:56 pm

It compiled fine with GCC 4.1-beta_20060120.

Stupid question. You mentioned something about recompiling KDE with visibility support?

Who? What? Why?

And I've always used the normal "emerge kde", but I've been reading about the split ebuilds.

I didn't want to have to worry about ten million split packages, but I've heard kde runs faster, and the split ebuilds pull the latest patches from SVN.

Is there a fairly simple and quick way to switch to the split ebuilds?

ktm · Post by **ktm** » Thu Jan 26, 2006 4:41 pm

This is very nice! Now we just need someone to tweak and play with gtk

martin.k · Post by **martin.k** » Thu Jan 26, 2006 5:17 pm

Thanx!
Patched qt works fine here with KDE-3.5.
Works little bit faster... I think so, but I can't state it on my AMD XP 2400+ box
I'll wait for KDE-3.5.1 to emerge it with smybol visibility

Gabrys · Post by **Gabrys** » Thu Jan 26, 2006 6:32 pm

Man, I love your ebuilds. You rock!

nxsty · Post by **nxsty** » Thu Jan 26, 2006 10:19 pm

no4b wrote:Thx for the ebuild. Btw. if it's so good, maybe fill the report on bugzilla and developers will add qt-copy patches to the official ebuild (for example available as USE flag). I used them on freebsd and there were no problems.

http://bugs.gentoo.org/show_bug.cgi?id=120464

seren · Post by **seren** » Fri Jan 27, 2006 2:25 am

what useflag do i need for visibility support?

also i pmed you

Gabrys · Post by **Gabrys** » Fri Jan 27, 2006 11:33 am

I think it's 'risky' which enables it.

xbb · Post by **xbb** » Fri Jan 27, 2006 1:13 pm

Thanks, works great, using risky flag too... no problems yet.

OBenY · Post by **OBenY** » Sat Jan 28, 2006 7:39 pm

Nxsty, what about pertty Kde improved patches? Is it possible to integrate them into your ebuild ?
More info available here: http://forums.gentoo.org/viewtopic-t-23 ... t-375.html

tost · Post by **tost** » Sat Jan 28, 2006 8:20 pm

I´m installing qt-3.3.5 with risky useflag at the moment..

I´ll post my results (of an improvment) later..

My KDE is very slow (split-ebuilds) so I think this ebuild could be very useful for lot´s of people, thanks a lot

tost

nxsty · Post by **nxsty** » Sat Jan 28, 2006 8:55 pm

OBenY wrote:Nxsty, what about pertty Kde improved patches? Is it possible to integrate them into your ebuild ?
More info available here: http://forums.gentoo.org/viewtopic-t-23 ... t-375.html

It shouldn't be harder than putting the pertty patch in files/ and applying it. but you might need to disable the rubberband patch that I also included and perhaps the corresponding patch from qt-copy. I can fix that the next time I update my overlay.

tost · Post by **tost** » Sat Jan 28, 2006 9:04 pm

Great work..

KDE is starting much faster

I recommend every people this patchset, very nice..

tost

wrc1944 · Post by **wrc1944** » Sun Jan 29, 2006 9:00 am

nxsty wrote:

You don't need to rebuild KDE to get the benefits from qt-copy, but you can rebuild it to enable symbol visibility but then the kde eclass needs some tweaking first. I'm going to write another post about that.

I must admit I'm still a bit confused. To clarify, does this mean if we've already built kde and qt (and world) with CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden set in /etc/make.conf, we DON'T need to rebuild kde, but only qt?

Or are we talking about -fvisibility-hidden, which I've sometimes seen appear on it's own in the kde gcc output (on my ~x86 gcc-3.4.5 and 4.1 systems).

So (assuming we already have kde built with-fvisibility-inlines-hidden set in /etc/make.conf), if we want to go all the way with this, we just setup the overlay, and do:

USE="risky" emerge qt

Is this correct? And any other "qt" apps besides kde might need to be re-merged?

I'll try anything to improve kde performance (even by 1%), as it's the only desktop environment I use these days.