[solved] Installation problems with Pyqt - locating old version of qmake
-
I am trying to instal Pyqt but I am new to qt and having some significant issues. I have installed Sip4.16.7 and it installed in /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
I then installed Qt5.4 and it has installed to /users/MyUsername/Qt
I then installed PyQt5.4.1 and tried to run the configure file but I obviously have an older version of qmake on my system as I get an error of Error: PyQt5 requires Qt v5.0 or later. You seem to be using v4.7.4. Use the
--qmake flag to specify the correct version of qmake. This is confirmed by typing qmake -v in the terminal and I get the output of QMake version 2.01a
Using Qt version 4.7.4 in /opt/anaconda1anaconda2anaconda3/libHow do I update my qmake to get Pyqt installed? I have set the qmake flag to look in --qmake=/Users/MyUsername/Qt/5.4/ios/bin/qmake but it comes with an error of: Error: Failed to determine the detail of your Qt installation. Try again using
the --verbose flag to see more detail about the problem.any help would be greatly appreciated, Im getting nowhere!
-
Hi and welcome to devnet,
You probably have Qt 4.7.4 bin folder in your PATH environment variable, remove it from there and it should go better.
Do you want to build PyQt for iOS ?
[edit: added missing word...]
-
Hi and welcome to devnet,
You probably have Qt 4.7.4 bin folder in your PATH environment variable, remove it from there and it should go better.
Do you want to build PyQt for iOS ?
[edit: added missing word...]
-
Sorry, there was a word missing… I meant the PATH environment variable.
-
echo $PATHto see what's inside that variableIf the bin dir of Qt 4 is in there, then PATH is modified somewhere like in e.g. your .profile file. If not there, then did you install it using macports/homebrew ?
-
echo $PATHto see what's inside that variableIf the bin dir of Qt 4 is in there, then PATH is modified somewhere like in e.g. your .profile file. If not there, then did you install it using macports/homebrew ?
When I type echo $PATH I get /Library/Frameworks/Python.framework/Versions/2.7/bin://anaconda/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin
I dont think I installed Qt4 unless it came with anaconda? I installed Qt5 using the installer on their website.
-
What does
which qmakereturn ? -
What else do you have in that folder ? That's a pretty unusual path
-
Then you can either:
- Remove that Qt 4.7 from your system
- Rename that folder while you build PyQt
- Prepend the path to your iOS qmake to PATH before you call PyQt configure script
-
Then you can either:
- Remove that Qt 4.7 from your system
- Rename that folder while you build PyQt
- Prepend the path to your iOS qmake to PATH before you call PyQt configure script
By the third option do you mean the following:
python configure.py --qmake=/Users/paulbaranowski1/Qt/5.4/ios/bin/qmake
because when I do this I get the following output:
Querying qmake about your Qt installation...
Determining the details of your Qt installation...
Error: Failed to determine the detail of your Qt installation. Try again using
the --verbose flag to see more detail about the problem.or is there something else I should be doing?
-
My bad, I misread the original error message. No, you doing it right. However, call it again with --verbose to see the reason why it fails.
-
My bad, I misread the original error message. No, you doing it right. However, call it again with --verbose to see the reason why it fails.
I get a huge chunk of text which I can copy if you want, but the end message is:
Check dependencies
Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 8.1'make[1]: *** [iphoneos-release] Error 65
make: *** [release-iphoneos] Error 2 -
Did you subscribe to Apple's iOS developer program ?
-
Because developing/testing directly on a device requires that subscription, but the emulator not.
-
Because developing/testing directly on a device requires that subscription, but the emulator not.
-
AFAIK, as soon as you want to run your application on your device, yes but again, it's an Apple constraint and it doesn't have anything to do with the framework your might be using.
