./configure -no-exceptions recommended in qt-copy
faure at kde.org
Mon Oct 6 22:25:30 BST 2008
On Friday 03 October 2008, Fred Emmott wrote:
> On Friday 03 October 2008 13:23:07 David Faure wrote:
> > Thiago skipped this part in his reply, which is the most important IMHO.
> > *IF* any KDE application wants to start using QtXmlPatterns, then it seems
> > we have to get rid of -no-exceptions in our qt-copy instructions.
> > So that's the real question. I assume you're asking because you have a
> > need for it in KDE code?
> Actually, it's non-KDE Qt code I'm working on; it does however mean that if
> packagers follow the recommendations in README.qt-copy (excluding the obvious
> -debug), will (and do) make packages that don't work with qt apps that say
> "need qt 4.n or above" even though they have qt 4.n.
README.qt-copy is for developers, NOT for packagers. It would be a bad mistake
for a distribution to follow the configuration listed there, since it's a "KDE only" setup,
and indeed doesn't match other users of Qt.
> Additionally, if as Thiago says, packagers build all of Qt (including
> xmlpatterns, assuming then without no-exceptions), then this means that users
> are being given a rather different Qt build to that which developers use
> (assuming developers follow README.qt-copy).
Well, not _that_ different. Why would "Qt compiled with xmlpatterns" behave
any differently from "Qt compiled without xmlpatterns" as far as KDE is concerned?
Besides, not all developerrs use qt-copy, I see many people using their distro's Qt
(although I would myself never do that, since adding debug output to Qt itself is
sometimes helpful to understand the way the app is using it).
OK, so no change needed in README.qt-copy, current recommendation is fine
as long as no kde code needs xmlpatterns.
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel