Errors ( like qmake: Syntax error: word unexpected (expecting ")") ) occur when configuring Qt environment.
-
Hi and welcome to devnet,
While this error doesn't ring a bell, I just wanted to check if I understood you correctly: are you calling configure again in an already built Qt source tree ? If so, that's wrong. You have to first call make confclean.
In any case I'd recommend doing an out of source build, so if something goes wrong or you want to test several configuration you can simply nuke the current build and start from a clean state.Hope it helps
-
This could be because of extracting of source code. You might have extracted <source>.zip just by right click and extract. Instead of try extracting using unzip -a <source>.zip. This should fix the issue.
-
SGaist
Thanks for your reply.
That is 50% correct, the build was the second try and Qt source tree exists.
However I tried again, as another user to build from a scratch, downloading Qt source code and unzip to other directory, (I think this is clean environment) and then configuring. The result was the same.
Besides, though I'd like to try make confclean just in case, there's no Makefile any longer. Thus I couldn't make confclean... -
Dheerendra
Thanks for your reply.
I just want make sure, my source codes is qt-everywhtere-opensource-src-4.8.6.tar.gz
I extracted it by
tar -xcvf qt-everywhtere-opensource-src-4.8.6.tar.gz
on command line.How to do "<source>.zip just by right click and extract." ?
Please let me know the detail of that.
I'm now being confused...Thanks.
-
I am checking error log now...
/home/ida/Qt/build/qt-everywhere-opensource-src-4.8.6/bin/qmake
This qmake is ELF 32-bit LSB executable, for ARM CPU.
Is this ok?
I think that /usr/bin/qmake (for x86-64 CPU) should be used for checking...
If so, how can I do to configure? -
Since your source code is already the tar.gz you should be safe.
The qmake built with your cross-compiled Qt should be for the same architecture as your host since it's a host tool. So there's something fishy going on.Can you try with:
@/configure -embedded arm -opensource -confirm-license -nomake demos -nomake examples -prefix $ZYNQ_QT_INSTALL@?
-
Watch out, fiddling with PATH can be hazardous especially when you are using several version of Qt while developing
-
You're welcome !
Since you have it up and running now, please update the thread title prepending [solved] so other forum users may know a solution has been found :)