Qt4 portage update

Message

caleb · Post by **caleb** » Thu Jun 16, 2005 6:17 pm

With the pending release of Qt4 very soon, I wanted to take a moment to update
the community on what kind of effect it will have on portage:

First, the installation is now FHS compliant - no more stuff going
into /usr/qt.

Previous Qt versions built one big library; this version builds 9 or 10
smaller ones (all installed into /usr/lib/qt4). Since the names are
different, as well as the sonames, there should not be any runtime linking
issues with a mixed installation.

Qt4 does not make use of the QTDIR environment variable like Qt3 did. This
means that automated build scripts, such as those with most KDE programs,
will still pick up the correct Qt3 programs (uic, moc, and qmake). For
programs that don't use these types of build scripts, ebuild modifications
may need to be made to tell the package which directory to pick up its binary
tools in (/usr/qt/3/bin for Qt3, /usr/bin for Qt4).

I currently don't have any plans for any type of xxx-config package to switch
between versions. After installing Qt4, those applications will be higher in
precedence in the PATH. If you need to run Qt3 applications, you will either
need to specify the full path or restructure your PATH to make it work.

Even though Trolltech split out the GUI libraries from the rest of the core
libraries, X11 is still a dependency for the whole package. The reason for
this is that, as of now, Trolltech hasn't provided a convenient way to build
a subset of the libraries - it's really an all or nothing thing. Eventually
once the development stabilizes a bit, I think it will be feasible to have a
gui and non-gui set of ebuilds.

All that said - the latest version in portage ( qt-4.0.0_rc1-r2 ) works and
installs great for me. At this point, it may be good for aches to try
testing the installation, as well as people who use non-traditional setups,
like icc, ulibc, or "interesting" CXXFLAGS. Be forewarned though, It's still "-*" masked. If you don't know what that means or how to work around it, then you probably shouldn't try to install the package right now.

At the moment, I don't know of any installable applications that make use of
this new Qt version, but they'll be springing up very soon. Hopefully we'll
be ready for them.

Thanks,
Caleb

mod edit: sticky --Earthwings
mod edit: unstuck --mark_alec

Dr. Z · Post by **Dr. Z** » Sat Jun 18, 2005 11:35 pm

I wonder if someone can illuminate the build status of the examples; I USE=examples and it seems they come
"partially" built, with .pro's and Makefiles and strange "Trolltech/.config" turds lying around, but no executables.

I do get some examples to compile with the normal

Code: Select all

qmake -project
qmake
make

I can get the very basic examples/layouts/basiclayouts to link by doing this, and it will run
IF I create an /etc/env.d/55qt4 with the line

Code: Select all

LDPATH=/usr/lib/qt4

otherwise no /usr/lib/qt4 in my /etc/ld.so.cache

BUT examples/mainwindows does not link. I get a lot of errors like this during the final link:

Code: Select all

g++  -o mainwindows main.o mainwindow.o main.o mainwindow.o mdichild.o main.o mainwindow.o main.o mainwindow.o main.o mainwindow.o moc_mainwindow.o moc_mdichild.o qrc_application.o qrc_mdi.o qrc_sdi.o   -L/usr/lib/qt4 -L/usr/lib/mysql -L/usr/lib/qt4 -lQtGui_debug -L/usr/X11R6/lib -lpng -lSM -lICE -lXi -lXrender -lXrandr -lXcursor -lfreetype -lfontconfig -lXext -lX11 -lm -lQtCore_debug -lz -ldl -lpthread
main.o(.text+0x0): In function `main':
sdi/main.cpp:34: multiple definition of `main'
main.o(.text+0x0):sdi/main.cpp:34: first defined here
mainwindow.o(.text+0x0): In function `MainWindow::MainWindow[not-in-charge]()':
sdi/mainwindow.cpp:34: multiple definition of `MainWindow::MainWindow[not-in-charge]()'
mainwindow.o(.text+0x0):sdi/mainwindow.cpp:34: first defined here

examples/tools/qtdemo doesn't compile; I get

Code: Select all

g++ -c -pipe -g -Wall -W -D_REENTRANT -DQT_CORE_LIB -DQT_GUI_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I. -I. -I. -o launcher.o launcher.cpp
launcher.cpp:30:24: QDomDocument: No such file or directory
launcher.cpp:31:40: QtAssistant/QAssistantClient: No such file or directory

/usr/include/qt4/QtXml/QDomDocument certainly exists, although QtAssistant/QAssistantClient does not (but /usr/lib/qt4/libQtAssistantClient_debug.a does).

I have

Code: Select all

=x11-libs/qt-4.0.0_beta2-r3 debug examples odbc sqlite accessibility

in my /etc/portage/packages.make and

Code: Select all

bash-2.05b# equery uses =x11-libs/qt-4.0.0_beta2-r3
[ Searching for packages matching =x11-libs/qt-4.0.0_beta2-r3... ]
[ Colour Code : set unset ]
[ Legend    : Left column  (U) - USE flags from make.conf              ]
[           : Right column (I) - USE flags packages was installed with ]
[ Found these USE variables for x11-libs/qt-4.0.0_beta2-r3 ]
 U I
 + + accessibility : Adds support for accessibility (eg 'at-spi' library)
 + + cups          : Add support for CUPS (Common Unix Printing System)
 + + debug         : Tells configure and the makefiles to build for debugging. Effects vary across packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES=nostrip too
 + + doc           : Adds extra documentation (API, Javadoc, etc)
 + + examples      : Install example source code
 - - firebird      : Adds support for the Firebird relational database
 + + gif           : Adds GIF image support
 - - ipv6          : Adds support for IP version 6
 + + jpeg          : Adds JPEG image support
 + + mng           : Adds support for libmng (MNG images)
 + + mysql         : Adds mySQL support
 - - nas           : Adds support for network audio sound
 - - nis           : Support for NIS/YP services
 + + odbc          : Adds ODBC Support (Open DataBase Connectivity)
 + + opengl        : Adds support for OpenGL
 + + postgres      : Adds support for the postgresql database
 + + png           : Adds support for libpng (PNG images)
 + + sqlite        : <unknown>
 - - xinerama      : Add support for the xinerama X11 extension, which allows you to stretch your display across multiple monitors
 + + zlib          : Adds support for zlib (de)compression
 + + debug         : Tells configure and the makefiles to build for debugging. Effects vary across packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES=nostrip too

Thank you for your help; I'd like to start by getting the examples working before I try anything else with Qt4.

yardbird · Post by **yardbird** » Sun Jun 19, 2005 12:31 am

caleb wrote:At the moment, I don't know of any installable applications that make use of
this new Qt version

KDE svn?

Great work Caleb, gonna try it soon.

caleb · Post by **caleb** » Sun Jun 19, 2005 12:55 pm

examples *should* install properly with the latest ebuild in portage - Trolltech has been changing the handling of that and I think they have it correct now.

They don't, however, have QtDesigner and QtAssistant headers installing properly. They told me it was fixed in the 061605 snapshot, but it doesn't look to be. If it isn't fixed in a more recent snapshot, I'll just have the ebuild install them manually.

Other than those issues, the package seems to work well for me.

Dr. Z · Post by **Dr. Z** » Sun Jun 19, 2005 5:56 pm

I can get my own simple projects to build, so the qt-4 package seems pretty sound to me. Thanks for the good work on this. According to the docs, USE=examples is supposed to _build_ the examples but this doesn't seem to be the case; at least "etcat files" doesn't show those executables. According to one bug report, beta2-r2 was failing to install because the examples didn't build. So at least -r3 seems to ignore these build failures. I think it might be better I just DON'T USE=examples; I HOPE that would just install the pristine examples directory for me to build myself (I think some of the intermediate build files are causing me problems).

http://bugs.gentoo.org/show_bug.cgi?id=92484#c6

One more thing; for some reason we are missing include/QVBoxWidget, although it is present in the Qt docs:

http://doc.trolltech.com/4.0/qvboxwidget.html

However it is also not listed on their "All Classes" doc page so this sounds like a Trolltech problem. In any event I can work around it by using QVBoxLayout.

Cheers!

FGA · Post by **FGA** » Tue Jun 28, 2005 12:58 pm

Seems QT4 has been released

http://www.trolltech.com

dani · Post by **dani** » Tue Jun 28, 2005 1:34 pm

FGA wrote:Seems QT4 has been released

http://www.trolltech.com

we had been waiting for a long time for Qt4.

now I'm waiting for an ebuild

caleb · Post by **caleb** » Tue Jun 28, 2005 2:01 pm

The ebuild is in portage, please let me know if anything doesn't work for you (bug report at bugs.gentoo.org is the preferred place to report problems).

asimon · Post by **asimon** » Tue Jun 28, 2005 2:20 pm

Cool! Qt4 released AND in portage. The weekend is saved.

PS: And don't miss The Qt 4 Dance.

Epyon · Post by **Epyon** » Tue Jun 28, 2005 4:00 pm

That video is just... wow...

asimon · Post by **asimon** » Tue Jun 28, 2005 6:48 pm

Is anyone able to run the demostrations (not examples) via qtdemo?

menetto · Post by **menetto** » Tue Jun 28, 2005 7:48 pm

Is it possible to have qt 3 and qt 4 installed next to each other?
I want to develop apps with qt 4 and obviously I need qt 4 to run them. But since no apps support them up to now, I will need qt 3 for those apps. Am I not going to hose my system by trying this?

dani · Post by **dani** » Tue Jun 28, 2005 7:55 pm

menetto wrote:Is it possible to have qt 3 and qt 4 installed next to each other?
I want to develop apps with qt 4 and obviously I need qt 4 to run them. But since no apps support them up to now, I will need qt 3 for those apps. Am I not going to hose my system by trying this?

Qt 4 uses slots.

http://www.gentoo.org/doc/en/handbook/h ... #doc_chap4

menetto · Post by **menetto** » Tue Jun 28, 2005 8:00 pm

dani wrote:
Qt 4 uses slots.

http://www.gentoo.org/doc/en/handbook/h ... #doc_chap4

So I guess all the apps will be able to find the appriopriate libs for qt? Because now there is a variable QTDIR which says where qt is. But what will that value be with two qt's? Does a qt4 app know that it needs the qt4 libs and a qt3 app that it needs the qt3 libs?

firephoto · Post by **firephoto** » Tue Jun 28, 2005 8:04 pm

It's all described by Caleb in the first post in this topic.

menetto · Post by **menetto** » Tue Jun 28, 2005 8:14 pm

firephoto wrote:It's all described by Caleb in the first post in this topic.

Woops, my mistake. Sorry, gonna emerge it right away. The only way is for the moment by path I presume, since it's masked with -*. Adding to package.unmask doesn't work.

/me is feeling like a total noob.

cocoliso · Post by **cocoliso** » Tue Jun 28, 2005 8:47 pm

hahah lets do the qt4 dance!:lol:

asimon · Post by **asimon** » Tue Jun 28, 2005 9:37 pm

If anyone wants to see very nice Qt4 demos (not to be confused with the examples)... well the Qt ebuild currently doesn't install them (thus they are not launchable from qtdemo, you'll see only a screenshot).

But I suppose the issue will be fixed in short time, it's trivial and a bug report is already filed.

dani · Post by **dani** » Wed Jun 29, 2005 12:22 pm

Wow, Qt compiles and works!

(@caleb: great work, I didn't expect it to be in portage that fast.)

qtdemo seems to make X creating a high CPU load, especially the nice animated navigation menu. Is that a problem of Qt, Qt for Linux, Qt for Gentoo or of the qtdemo?

irondog · Post by **irondog** » Wed Jun 29, 2005 12:45 pm

Does anybody have any clue when KDE is QT4 ready?

Is it a matter of weeks, months, years?

dani · Post by **dani** » Wed Jun 29, 2005 12:50 pm

irondog wrote:Does anybody have any clue when KDE is QT4 ready?

Is it a matter of weeks, months, years?

KDE 4 will use Qt4. I think the next version of KDE will be 3.5 and after that they will begin working to port KDE to Qt4. So it will take a long time.

caleb · Post by **caleb** » Wed Jun 29, 2005 2:31 pm

menetto wrote: Woops, my mistake. Sorry, gonna emerge it right away. The only way is for the moment by path I presume, since it's masked with -*. Adding to package.unmask doesn't work.

You can put -* into package.keywords and it should work.

asimon · Post by **asimon** » Wed Jun 29, 2005 3:33 pm

dani wrote:I think the next version of KDE will be 3.5 and after that they will begin working to port KDE to Qt4. So it will take a long time.

Some KDE developers have already begun with the porting to Qt4.
KDE 3.4.2 will be released Wednesday, 27th July 2005.
KDE 3.5 has no time based schedule. It will be released somewhen in September or October and will be the last Qt 3 based KDE. Afterwards everyone will work on KDE 4 which will be based on Qt4. KDE 4 will be released in 2006, maybe around September.

dani wrote:qtdemo seems to make X creating a high CPU load, especially the nice animated navigation menu. Is that a problem of Qt, Qt for Linux, Qt for Gentoo or of the qtdemo?

The current "acceleration" architecture of X sucks. But as you can read in recent news reports developers at Troll Tech are already working on a replacement.

pops45042 · Post by **pops45042** » Thu Jun 30, 2005 10:45 pm

The ebuild for QT4 dies on my system. See my original thread here
http://forums.gentoo.org/viewtopic-t-354829.html

Paul

Headrush · Post by **Headrush** » Thu Jun 30, 2005 11:40 pm

no problems here.

Qt4 portage update

Qt4 portage update

examples

Re: Qt4 portage update

Re: examples