View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002862 | Slicer4 | Core: Building (CMake, Superbuild) | public | 2013-01-09 18:08 | 2014-03-06 04:54 |
Reporter | markmichalski | Assigned To | jcfr | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | Slicer 4.2.2-1 | ||||
Target Version | Slicer 4.3.0 | Fixed in Version | Slicer 4.3.0 | ||
Summary | 0002862: Failure to recognize qmake on cmake | ||||
Description | On OSX 10.8.2 When Attempting: ./configure -prefix ../qt-everywhere-opensource-build-4.7.4 -debug-and-release -opensource -confirm-license -no-qt3support -webkit -arch x86_64 -nomake examples -nomake demos -sdk /Developer/SDKs/MacOSX10.5.sdk/ The configure fails. So I attempted to do it as with linux: ./configure -prefix ../qt-everywhere-opensource-build-4.7.4 -debug-and-release -opensource -confirm-license -no-qt3support -webkit -nomake examples -nomake demos This works. However, there is no SDK1.2 or equivalent to point CMAKE QT_QMAKE_EXECUTABLE path. Attempted ~/build/qt-everywhere-opensource-build-4.7.4/bin/qmake. CMake does not recognize this as a qmake executable and states qt4.7.4 is not on my machine. Thanks for your help! | ||||
Tags | No tags attached. | ||||
What is the output of the following command ? $ /path/to/qmake -query |
|
input: returns: |
|
By "/path/to/qmake", I mean that you should look for the executable "qmake" in your qt build directory .. and then execute the command appending the "-query" param. |
|
Of course, apologies. Output: QT_INSTALL_PREFIX:/Users/markmichalski/build/qt-everywhere-opensource-build-4.7.4 |
|
I am assuming this a MacOSX build since the path starts with /Users, from your first note, you mentioned qt could not be build on MacOSX. Did you manage to compile Qt on mac ? If you do the following:
You are reporting that it fails to configure Slicer. Is that correct ? |
|
Param - That was true, but seems fine now...perhaps it was because I was using: as opposed to the full path: I'm not sure. In any case, seems to be working alright now. Thanks! M |
|
Hi Mark, Good to know that the problem doesn't occur any more. To set QT_QMAKE_EXECUTABLE, full path have indeed to be passed. |
|
Closing resolved issues that have not been updated in more than 3 months |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2013-01-09 18:08 | markmichalski | New Issue | |
2013-01-09 18:08 | markmichalski | Status | new => assigned |
2013-01-09 18:08 | markmichalski | Assigned To | => jcfr |
2013-01-09 18:18 | jcfr | Target Version | => Slicer 4.2.3 |
2013-01-09 18:18 | jcfr | Note Added: 0007641 | |
2013-01-09 18:18 | jcfr | Status | assigned => feedback |
2013-01-09 18:36 | markmichalski | Note Added: 0007642 | |
2013-01-09 18:49 | jcfr | Note Added: 0007643 | |
2013-01-09 18:55 | markmichalski | Note Added: 0007644 | |
2013-01-09 19:00 | jcfr | Note Added: 0007646 | |
2013-01-10 05:12 | markmichalski | Note Added: 0007647 | |
2013-01-10 05:39 | jcfr | Note Added: 0007648 | |
2013-01-10 05:39 | jcfr | Status | feedback => resolved |
2013-01-10 05:39 | jcfr | Fixed in Version | => Slicer 4.2.3 |
2013-01-10 05:39 | jcfr | Resolution | open => fixed |
2013-02-12 09:39 | jcfr | Target Version | Slicer 4.2.3 => Slicer 4.3.0 |
2013-02-12 09:40 | jcfr | Fixed in Version | Slicer 4.2.3 => Slicer 4.3.0 |
2014-03-06 04:53 | jcfr | Note Added: 0010770 | |
2014-03-06 04:54 | jcfr | Status | resolved => closed |