Opened 15 years ago
Closed 3 years ago
#21884 closed defect (wontfix)
No qmake in /opt/local/bin/qmake
| Reported by: | dweber@… | Owned by: | michaelld (Michael Dickens) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.1 |
| Keywords: | qmake doxygen | Cc: | hsivank@…, dershow, mf2k (Frank Schima), sharky@… |
| Port: | qt4-mac |
Description
There is only a symlink to qmake-mac, rather than qmake, i.e.:
/opt/local/bin/qmake-mac -> /opt/local/libexec/qt4-mac/bin/qmake*
There may be a good reason not to create a similar symlink, i.e.:
/opt/local/bin/qmake -> /opt/local/libexec/qt4-mac/bin/qmake*
However, other build systems or applications may assume there is a 'qmake' in the bin path (they may not look for 'qmake-mac' or use some kind of regex to find qmake* in the bin path).
For example, I'm playing around with doxygen in my user svn sandbox, see
http://trac.macports.org/browser/users/dweber/textproc/doxygen
Unfortunately, doxygen does not provide a build config option to define the qmake binary path. When built with the +wizard variant, it fails to find qmake. (Strangely, it does get the QTDIR env and it can find moc in /opt/local/libexec/qt4-mac/bin/, but not qmake).
There may be other solutions for this issue with doxygen, but it's likely that other builds or apps will look for 'qmake' in the bin path.
Can we have a symlink for 'qmake' in the bin path?
Change History (14)
comment:1 Changed 15 years ago by hsivank@…
| Cc: | hsivank@… added |
|---|
comment:3 Changed 15 years ago by dershow
I was trying to build another Qt application (sqlitemanager) that failed, but it used to build fine. I was able to explicitly pass it the path to qmake to get it to work, but not finding qmake in my path did confuse it and make it more difficult.
comment:4 Changed 14 years ago by mf2k (Frank Schima)
| Owner: | changed from erickt@… to nomaintainer@… |
|---|
comment:6 Changed 14 years ago by mf2k (Frank Schima)
| Owner: | changed from nomaintainer@… to macports-tickets@… |
|---|
comment:8 Changed 14 years ago by michaelld (Michael Dickens)
Is this issue still relevant as of r72571 with qt4-mac being at 4.7.0?
comment:9 Changed 14 years ago by michaelld (Michael Dickens)
| Owner: | changed from macports-tickets@… to michaelld@… |
|---|---|
| Status: | new → assigned |
comment:10 Changed 13 years ago by michaelld (Michael Dickens)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I'm closing this ticket; Qt has made much progress, and this ticket is not longer relevant IMHO. If you disagree, please reopen this ticket and add your comments.
comment:11 follow-up: 14 Changed 3 years ago by vitalyster
This is still an issue with latest qt5 package: qmake is not on PATH, but present in libexec directory
comment:12 Changed 3 years ago by vitalyster
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
comment:13 Changed 3 years ago by michaelld (Michael Dickens)
This issue is with regard to Qt4, not Qt5. That said, both Qt4 and Qt5 install into libexec and then we set environment variables to find the relevant qmake. We have been doing this for a long time. While folks have complained here and there, the overall situation has been very successful, and is thus something we are unlikely to change. We feel that it is not a huge burden for projects to look in alternative paths for executables, which includes those for all Qt via MacPorts.
comment:14 Changed 3 years ago by michaelld (Michael Dickens)
| Resolution: | → wontfix |
|---|---|
| Status: | reopened → closed |
Replying to vitalyster:
This is still an issue with latest qt5 package: qmake is not on PATH, but present in libexec directory
This is all true, but does not represent reasoning as to why the installs should be changed. I'm closing again.
Cc Me!