The latest version of Kile ( 1.3 ) won't build under rc4, since QT has to be built with the -no-stl option. The author said I should add: #define QT_NO_STL to the begining of the following files: fileFilter.cpp multiFile.cpp qplotdialog.cpp qplotmaker.cpp rawGnu.cpp That helped to get it compiled.
I've posted on kde-devel asking: The qt-copy readme advises to turn qt's STL support off explicitly. Right now it's enabled in Gentoo. There have only been 2 problems with it: one in kopete cvs (fixed upstream) and on in kile (fix is simply to add #define QT_NO_STL in several source files, and may be added upstream). Since it's aparently so easy to get around the stl support even if it's enabled - a simple #define passed to the qt headers - I ask myself if all affected apps (just 2 known so far) should just have it and not care if there's stl support or no. Of course, the underlying question is, does anything _need_ or use the qt stl support? (At least anything on Gentoo --> Linux). --------- Another reason not to change things is that it'd force all kdelibs packages (incl. 3.0.x ones) to be recompiled or (widget) plugins won't load.
Question: did the kile author say he'd merge these changes into the upstream sources?
I've added this fix to the ebuild in portage.
