You cannot configure qt separately within a top-level build
-
@Pablo-J.-Rogina : Still it gives the same error.
-
-
@Pablo-J.-Rogina : I just mounted my sd card under /mnt/raspberry-rootfs
@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.
@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.
@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.
-
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.
