You cannot configure qt separately within a top-level build
-
Hi
You are not stating Qt version, platform etc so hard to geuss at.Might be this ?
https://bugreports.qt.io/browse/QTBUG-56049 -
wrote on 23 May 2018, 13:07 last edited by
@Vivx701 it looks like you're trying to cross compile (-device-option CROSS_COMPILE=...) so are you following this guide? It worked for me with Raspbian Stretch, Qt 5.10.1 and Pi Zero W
Just in case, you stated "for Raspberry-Pi 3" but you shown configurating it for RPi 2 -> "-device linux-rasp-pi2-g++" -
@Vivx701 it looks like you're trying to cross compile (-device-option CROSS_COMPILE=...) so are you following this guide? It worked for me with Raspbian Stretch, Qt 5.10.1 and Pi Zero W
Just in case, you stated "for Raspberry-Pi 3" but you shown configurating it for RPi 2 -> "-device linux-rasp-pi2-g++"wrote on 23 May 2018, 13:39 last edited by@Pablo-J.-Rogina Iam not building for rasbian . My target os is fedberry
-
@Pablo-J.-Rogina Iam not building for rasbian . My target os is fedberry
wrote on 23 May 2018, 13:42 last edited by@Vivx701 said in You cannot configure qt separately within a top-level build:
fedberry
Ok, it would be better to have stated it previously :-) (saving you and me a couple of posts...)
Even with that, I guess the suggested guide would still apply from step #5 onwards, wouldn't it?
-
@Vivx701 said in You cannot configure qt separately within a top-level build:
fedberry
Ok, it would be better to have stated it previously :-) (saving you and me a couple of posts...)
Even with that, I guess the suggested guide would still apply from step #5 onwards, wouldn't it?
wrote on 23 May 2018, 13:49 last edited by@Pablo-J.-Rogina : Still it gives the same error.
-
@Pablo-J.-Rogina : Still it gives the same error.
wrote on 23 May 2018, 13:58 last edited by -
wrote on 23 May 2018, 13:59 last edited by Vivx701
@Pablo-J.-Rogina : I just mounted my sd card under /mnt/raspberry-rootfs
-
@Pablo-J.-Rogina : I just mounted my sd card under /mnt/raspberry-rootfs
wrote on 23 May 2018, 14:01 last edited by@Vivx701 Ok, it's up to you. All I can say it's the guide helped me achieving the goal of cross-compiling Qt for RPi
Roger over and out! -
Hi,
You seem to be building Qt from within a directory that's inside the sources, is that correct ?
If so, then that's likely the problem. You should build Qt either within the top folder of the sources or even better in a folder outside of the sources.
-
Hi,
You seem to be building Qt from within a directory that's inside the sources, is that correct ?
If so, then that's likely the problem. You should build Qt either within the top folder of the sources or even better in a folder outside of the sources.
wrote on 23 May 2018, 14:31 last edited by@SGaist Now i created a directory outside Qt source code and tried running this . see the output at the end same error.
bash-4.4$ ../qt-everywhere-opensource-src-5.9.5/configure -recheck-all -opengl es2 -device linux-rasp-pi3-g++ -device-option CROSS_COMPILE=/home/alokin/raspberry/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- -sysroot /mnt/raspberry-rootfs -opensource -confirm-license -optimized-qmake -reduce-exports -release -make libs -prefix /usr/local/Qt_595-raspberry/ -qt-libpng -qt-zlib -qt-libjpeg -qt-pcre -qt-freetype -skip qtwebengine -force-debug-info -nomake tests
- cd qtbase
- /home/alokin/Qt5.9/qt-everywhere-opensource-src-5.9.5/qtbase/configure -top-level -recheck-all -opengl es2 -device linux-rasp-pi3-g++ -device-option CROSS_COMPILE=/home/alokin/raspberry/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- -sysroot /mnt/raspberry-rootfs -opensource -confirm-license -optimized-qmake -reduce-exports -release -make libs -prefix /usr/local/Qt_595-raspberry/ -qt-libpng -qt-zlib -qt-libjpeg -qt-pcre -qt-freetype -skip qtwebengine -force-debug-info -nomake tests
Preparing build tree...
Creating qmake...
.Done.
Project ERROR: You cannot configure qt separately within a top-level build.
-
Hi,
You seem to be building Qt from within a directory that's inside the sources, is that correct ?
If so, then that's likely the problem. You should build Qt either within the top folder of the sources or even better in a folder outside of the sources.
wrote on 23 May 2018, 14:41 last edited by@SGaist This time iam trying to build with in Qt source code directory , see the output . same error
./configure -recheck-all -opengl es2 -device linux-rasp-pi3-g++ -device-option CROSS_COMPILE=/home/alokin/raspberry/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- -sysroot /mnt/raspberry-rootfs -opensource -confirm-license -optimized-qmake -reduce-exports -release -make libs -prefix /usr/local/Qt_595-raspberry/ -qt-libpng -qt-zlib -qt-libjpeg -qt-pcre -qt-freetype -skip qtwebengine -force-debug-info -nomake tests
- cd qtbase
- /home/alokin/Qt5.9/qt-everywhere-opensource-src-5.9.5/qtbase/configure -top-level -recheck-all -opengl es2 -device linux-rasp-pi3-g++ -device-option CROSS_COMPILE=/home/alokin/raspberry/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- -sysroot /mnt/raspberry-rootfs -opensource -confirm-license -optimized-qmake -reduce-exports -release -make libs -prefix /usr/local/Qt_595-raspberry/ -qt-libpng -qt-zlib -qt-libjpeg -qt-pcre -qt-freetype -skip qtwebengine -force-debug-info -nomake tests
Creating qmake...
.Done.
Project ERROR: You cannot configure qt separately within a top-level build.
-
Are you doing that from clean sources ?
If not, you should nuke them as well as the build folders you used and start over with an out of source build.
-
Are you doing that from clean sources ?
If not, you should nuke them as well as the build folders you used and start over with an out of source build.
wrote on 24 May 2018, 04:46 last edited by -
wrote on 24 May 2018, 13:40 last edited by Vivx701
hello guys , finally iam able to build Qt after making two blank files named
1.) .qmake.stash
2.) .qmake.super
in build directory. So the problem is happening due to not creating this two files in the configuring step. I don't know why configuring script is behaving like this. -
wrote on 11 Aug 2020, 20:34 last edited by
Adding .qmake.super seemed that have fixed my issue as well. Has anyone found out why it wasn't created to begin with?
-
wrote on 3 Jan 2021, 02:24 last edited by
Cloned GIT folder into Mint Linux 20, I had a failed configure in the root directory. Removed .qmake.super file from the root QT5 folder, then configured again within the QT5-build folder without error.