Summary: | QT project templates don't specify $PATH or $QTDIR | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Viktor S. Grishchenko <gritzko> |
Component: | Build tools: QMake | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
patch to workaround $QTDIR/$PATH issue
a new patch for HEAD |
Description
Viktor S. Grishchenko
2003-11-08 13:10:44 UTC
Can you please specify your KDevelop version? I believe we can nothing to do with that. I don't know a good way to determine QTDIR and PATH for a qmake based project. Closing as "wontfix". Reopen if you feel I am wrong. Created attachment 3287 [details]
patch to workaround $QTDIR/$PATH issue
IMHO, explicitly giving precedence to $QTDIR/bin is not a bad thing.
It may help in cases when $QTDIR is not on $PATH or multiple QT installations
are present.
A patch proposed. Created attachment 3375 [details]
a new patch for HEAD
The same issue.
$QTDIR/bin/ must have precedence in $PATH
Hi all, I have not tested the patches but seems to be same issue as bug 74465. Kdevelop does not read KDEDIR and QTDIR environment variable when launched from kde menu ... but does consider those variables when lauched from konsole. I have Qt installed in /opt/qt-3.2.0 and kde in /opt/kde-3.2.0, and the only good way to have kdevelop work properly with Kde and Qt projects is to run kdevelop from konsole (where KDEDIR and QTDIR are set). Is it a kdevelop bug or a kde bug or ... maybe not a bug because how can we tell kdevelop or kde to read the user .bashrc file to get the variables ? Hope this comment will help Fabien This is changed in recent versions of KDevelop SVN. We now have an option to set the Qt directory |