Re: [Qbs] Mingw issues
On 07/04/20 23:04, Richard Weickelt wrote: > I think qbs-setup-toolchains got confused by the "." in the toolchain > prefix. It is usually not expected. The heuristics have been improved in Qbs > 1.16. Could you try if it works with the release candidate of Qt Creator > 4.12 and otherwise submit a patch for > https://code.qt.io/cgit/qbs/qbs.git/tree/src/app/qbs-setup-toolchains/gccprobe.cpp > ? Here it is: https://codereview.qt-project.org/c/qbs/qbs/+/296870 I wait on the CI to see whether this breaks something on Windows, since I didn't test Windows myself. :-) Ciao, Alberto -- http://www.mardy.it - Geek in un lingua international ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Mingw issues
> It looks like the value of > `profiles.mxe-i686-w64-mingw32-static.cpp.toolchainPrefix` was > incomplete (you can see it from the config pasted above). It should have > been "i686-w64-mingw32.static-", and after changing it to that value, > the build started. > > So, actually, my problem is solved. It would be super cool if QBS was so > smart to automatically detect the correct baseProfile to be used when I > point it to a qmake provided by MXE, and I still need to figure out why > the toolchainPrefix was only set to `i686-w64`. I think qbs-setup-toolchains got confused by the "." in the toolchain prefix. It is usually not expected. The heuristics have been improved in Qbs 1.16. Could you try if it works with the release candidate of Qt Creator 4.12 and otherwise submit a patch for https://code.qt.io/cgit/qbs/qbs.git/tree/src/app/qbs-setup-toolchains/gccprobe.cpp ? ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Mingw issues
On 05/04/20 22:48, Richard Weickelt wrote: > Does your toolchain setup work without Qt? Maybe build a plain c++ hello > world app. > > Is the deduced qbs.architecture correct? The architecture is unset (I cannot see it with `qbs config`, at least). But looking at the configuration I understood where the problem was: I didn't set up the base profile correctly: == $ qbs config --list [...] profiles.gcc.cpp.toolchainInstallPath: "/usr/bin" profiles.gcc.qbs.toolchain: "gcc" profiles.mxe-i686-w64-mingw32-static.cpp.toolchainInstallPath: "/mnt/Lavoro/mxe/mxe-qt5.9/usr/bin" profiles.mxe-i686-w64-mingw32-static.cpp.toolchainPrefix: "i686-w64-" profiles.mxe-i686-w64-mingw32-static.qbs.targetPlatform: "windows" profiles.mxe-i686-w64-mingw32-static.qbs.toolchain: ["mingw", "gcc"] profiles.mxe-qt59-i686-w64-mingw32-static.baseProfile: "gcc" profiles.mxe-qt59-i686-w64-mingw32-static.moduleProviders.Qt.qmakeFilePaths: "/mnt/Lavoro/mxe/mxe-qt5.9/usr/i686-w64-mingw32.static/qt5/bin/qmake" [...] == Setting the base profile to "mxe-i686-w64-mingw32-static" made me progress a bit: == ERROR: /home/mardy/src/git/mappero/lib/Mappero/Mappero.qbs:3:1 Error while handling product 'Mappero': /usr/local/share/qbs/imports/qbs/Probes/GccProbe.qbs:56:16 Error: Error running '/mnt/Lavoro/mxe/mxe-qt5.9/usr/bin/i686-w64-g++': execve: No such file or directory == It looks like the value of `profiles.mxe-i686-w64-mingw32-static.cpp.toolchainPrefix` was incomplete (you can see it from the config pasted above). It should have been "i686-w64-mingw32.static-", and after changing it to that value, the build started. So, actually, my problem is solved. It would be super cool if QBS was so smart to automatically detect the correct baseProfile to be used when I point it to a qmake provided by MXE, and I still need to figure out why the toolchainPrefix was only set to `i686-w64`. Ciao, Alberto -- http://www.mardy.it - Geek in un lingua international ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
[Qbs] Mingw issues
Hi all! I've a feeling I've met this problem before, but I cannot remember what the solution was. So here I am again :-) I'm trying to build an application for Linux, using QBS with MXE. I've setup my toolchain like this: MXE_DIR=/mnt/Lavoro/mxe/mxe-qt5.9 qbs setup-toolchains $MXE_DIR/usr/bin/i686-w64-mingw32.static-g++ mxe-i686-w64-mingw32.static # The above didn't recognize my compiler, so these two were needed: qbs config profiles.mxe-i686-w64-mingw32-static.cpp.cxxCompilerName:i686-w64-mingw32.static-g++ qbs config profiles.mxe-i686-w64-mingw32-static.cpp.cCompilerName:i686-w64-mingw32.static-gcc # Then, add Qt: qbs setup-qt $MXE_DIR/usr/i686-w64-mingw32.static/qt5/bin/qmake mxe-qt59-i686-w64-mingw32-static # use the MXE toolchain: qbs config profiles.mxe-qt59-i686-w64-mingw32-static.baseProfile:profiles.mxe-i686-w64-mingw32-static But then, when I run qbs on my program, it spits out a few errors: Build graph does not yet exist for configuration 'default'. Starting from scratch. Resolving project for configuration default Setting up Qt at '/mnt/Lavoro/mxe/mxe-qt5.9/usr/i686-w64-mingw32.static/qt5/bin/qmake'... Qt was set up successfully. ERROR: /home/mardy/src/git/mappero/lib/Mappero/Mappero.qbs:3:1 Error while handling product 'Mappero': /home/mardy/src/git/mappero/lib/Mappero/Mappero.qbs:61:5 Module Qt.core could not be loaded. /home/mardy/src/git/mappero/lib/Mappero/Mappero.qbs:62:5 Module Qt.gui could not be loaded. /home/mardy/src/git/mappero/lib/Mappero/Mappero.qbs:63:5 Module Qt.qml could not be loaded. /home/mardy/src/git/mappero/lib/MapperoUi/MapperoUi.qbs:3:1 Error while handling product 'MapperoUi': /home/mardy/src/git/mappero/lib/MapperoUi/MapperoUi.qbs:49:5 Module Qt.core could not be loaded. /home/mardy/src/git/mappero/lib/MapperoUi/MapperoUi.qbs:50:5 Module Qt.quick could not be loaded. /home/mardy/src/git/mappero/src/qt/qt.qbs:4:1 Error while handling product 'mappero': /usr/local/share/qbs/imports/qbs/base/QtGuiApplication.qbs:32:5 Module Qt.gui could not be loaded. /home/mardy/src/git/mappero/src/qt/qt.qbs:125:5 Module Qt.core could not be loaded. /home/mardy/src/git/mappero/src/qt/qt.qbs:126:5 Module Qt.quick could not be loaded. /home/mardy/src/git/mappero/src/qt/qt.qbs:128:5 Module Qt.widgets could not be loaded. /home/mardy/src/git/mappero/src/qt/qt.qbs:135:5 Module Qt.concurrent could not be loaded. These modules seem, however, to have been proeprly setup. I do have, for example: default/genmodules/Qt/c0b33115f511456a/modules/Qt/core/core.qbs Any hints on how to further debug the issue? Ciao, Alberto -- http://www.mardy.it - Geek in un lingua international ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
