Red Hat Bugzilla – Bug 225394
The Qt4 support in 3.3.5 is broken
Last modified: 2008-05-06 15:07:39 EDT
Description of problem:
The Qt4 support of kdevelop is broken.
You can set the path to the Qt4 tools, but the tools of Qt3 will be called.
Version-Release number of selected component (if applicable):
every time you try to create an Qt4 project
Steps to Reproduce:
1. create an new Qt project
2. set under the C++ extras Qt4 an add the path to Qt4
The Qt3 tools will used.
That the Qt4 tools will used.
This is solved in kdevelop 3.4, witch was released today.
So an simply update will fix it.(tested with the binary package for FC5 from
kdevelop.org) Same for FC6.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.