Re: [Development] tools/configure with mingw build error
On 29.08.2012 02:02, Rohan McGovern wrote: >> >> Is there a list which configurations are checked by the CI? >> > > Yes, you can check the list from testresults.qt-project.org, e.g. > http://testresults.qt-project.org/ci/QtBase_master_Integration/latest-success/ For the quality gate checks such a short list is OK. > > MinGW used to be tested by CI, but the compiler frequently crashed > (internal compiler error), so it was removed - there are some links from > this task: https://bugreports.qt-project.org/browse/QTQAINFRA-549 > >> For instance CMake checks >30 Windows and >60 Linux/Unix configuration on a >> daily basis (even jom) >> http://open.cdash.org/index.php?project=CMake >> > > Impressive for sure, but note it is not really fair to compare that with > Qt's CI, since Qt's needs to pass before code is allowed in (quality gate) > while most of the configurations in the above link apparently don't > (not a quality gate). Maybe it is possible to test on a daily/weekly basis much more configurations, and to only send an email when something breaks. Peter ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
Peter Kümmel said: > On 28.08.2012 21:14, Peter Kümmel wrote: > > On 28.08.2012 20:46, Peter Kümmel wrote: > > But also jom fails, I thought jom could also handle mingw makefiles? > >>> > >>> No, Jom only handles NMake makefiles, afaik. > >>> > >> > >> Checked it again: I could build qt/4.8 with jom. > >> > >> So I would say the Makefiles in Qt5 are broken (at least for configure). > >> > > > > Also the makefile for qmake doesn't work. > > > > In Qt 4.8 for qmake there are two makefiles for g++: > > Makefile.win32-g++ and Makefile.win32-g++-sh > > > > In qtbase/qmake there is only Makefile.win32-g++. > > The two files were merged: > > > > https://qt.gitorious.org/qt/qtbase/commit/d9bf972e2b5f6bace5b7be350a70b4207e320692 > > > > Seems nobody have used mingw/jom since 6 months. > > > > This could be all checked by CI, but it isn't. > > Is there a list which configurations are checked by the CI? > Yes, you can check the list from testresults.qt-project.org, e.g. http://testresults.qt-project.org/ci/QtBase_master_Integration/latest-success/ MinGW used to be tested by CI, but the compiler frequently crashed (internal compiler error), so it was removed - there are some links from this task: https://bugreports.qt-project.org/browse/QTQAINFRA-549 > For instance CMake checks >30 Windows and >60 Linux/Unix configuration on a > daily basis (even jom) > http://open.cdash.org/index.php?project=CMake > Impressive for sure, but note it is not really fair to compare that with Qt's CI, since Qt's needs to pass before code is allowed in (quality gate) while most of the configurations in the above link apparently don't (not a quality gate). ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28.08.2012 21:14, Peter Kümmel wrote: > On 28.08.2012 20:46, Peter Kümmel wrote: But also jom fails, I thought jom could also handle mingw makefiles? >>> >>> No, Jom only handles NMake makefiles, afaik. >>> >> >> Checked it again: I could build qt/4.8 with jom. >> >> So I would say the Makefiles in Qt5 are broken (at least for configure). >> > > Also the makefile for qmake doesn't work. > > In Qt 4.8 for qmake there are two makefiles for g++: > Makefile.win32-g++ and Makefile.win32-g++-sh > > In qtbase/qmake there is only Makefile.win32-g++. > The two files were merged: > > https://qt.gitorious.org/qt/qtbase/commit/d9bf972e2b5f6bace5b7be350a70b4207e320692 > > Seems nobody have used mingw/jom since 6 months. > This could be all checked by CI, but it isn't. Is there a list which configurations are checked by the CI? For instance CMake checks >30 Windows and >60 Linux/Unix configuration on a daily basis (even jom) http://open.cdash.org/index.php?project=CMake > Peter > > >> Peter >> ___ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development >> > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28.08.2012 21:12, marius.storm-ol...@nokia.com wrote: > On 28/08/2012 13:46, ext Peter Kümmel wrote: >> On 28.08.2012 19:59, marius.storm-ol...@nokia.com wrote: >>> On 28/08/2012 12:48, ext Peter Kümmel wrote: But also jom fails, I thought jom could also handle mingw makefiles? >>> >>> No, Jom only handles NMake makefiles, afaik. >> >> Checked it again: I could build qt/4.8 with jom. >> >> So I would say the Makefiles in Qt5 are broken (at least for >> configure). > > What was the mkspec for Qt 4.8 when you built it with Jom? mkspecs/win32-g++-4.6 > > (Look at the contents of /.qmake.cache and look at the QMAKESPEC > variable) > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28.08.2012 20:46, Peter Kümmel wrote: >>> >>> But also jom fails, I thought jom could also handle mingw makefiles? >> >> No, Jom only handles NMake makefiles, afaik. >> > > Checked it again: I could build qt/4.8 with jom. > > So I would say the Makefiles in Qt5 are broken (at least for configure). > Also the makefile for qmake doesn't work. In Qt 4.8 for qmake there are two makefiles for g++: Makefile.win32-g++ and Makefile.win32-g++-sh In qtbase/qmake there is only Makefile.win32-g++. The two files were merged: https://qt.gitorious.org/qt/qtbase/commit/d9bf972e2b5f6bace5b7be350a70b4207e320692 Seems nobody have used mingw/jom since 6 months. Peter > Peter > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28/08/2012 13:46, ext Peter Kümmel wrote: > On 28.08.2012 19:59, marius.storm-ol...@nokia.com wrote: >> On 28/08/2012 12:48, ext Peter Kümmel wrote: >>> But also jom fails, I thought jom could also handle mingw >>> makefiles? >> >> No, Jom only handles NMake makefiles, afaik. > > Checked it again: I could build qt/4.8 with jom. > > So I would say the Makefiles in Qt5 are broken (at least for > configure). What was the mkspec for Qt 4.8 when you built it with Jom? (Look at the contents of /.qmake.cache and look at the QMAKESPEC variable) -- .marius ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28.08.2012 19:59, marius.storm-ol...@nokia.com wrote: > On 28/08/2012 12:48, ext Peter Kümmel wrote: >> On 28.08.2012 19:27, marius.storm-ol...@nokia.com wrote: >>> On 28/08/2012 12:16, ext Peter Kümmel wrote: Have I missed something or is building with mingw in cmd.exe not supported? >>> >>> This is not your fault, it's the rubenvb release which is broken, as the >>> GNU Make tool provided is not properly splitting the file paths. Thus, >>> mingw32-make is trying to stat the wrong files and cannot find all the >>> files required. >>> >>> If you're feeling adventurous, I've found that you can do a binary patch >>> by simply replacing the pattern 0x003a3b00 with 0x003b3b00 in >>> mingw32-make.exe, and it should do the path splitting correctly and find >>> the required files. >>> >>> Note that this is just a work-around, and Ruben will have to correct the >>> way he cross-compiles the MinGW tools. >>> >>> See >>> http://sourceforge.net/tracker/?func=detail&aid=3545000&group_id=202880&atid=983354 >>> for details. >> >> Ahh thanks. >> >> But also jom fails, I thought jom could also handle mingw makefiles? > > No, Jom only handles NMake makefiles, afaik. > Checked it again: I could build qt/4.8 with jom. So I would say the Makefiles in Qt5 are broken (at least for configure). Peter ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28/08/2012 12:48, ext Peter Kümmel wrote: > On 28.08.2012 19:27, marius.storm-ol...@nokia.com wrote: >> On 28/08/2012 12:16, ext Peter Kümmel wrote: >>> Have I missed something or is building with mingw in cmd.exe not supported? >> >> This is not your fault, it's the rubenvb release which is broken, as the >> GNU Make tool provided is not properly splitting the file paths. Thus, >> mingw32-make is trying to stat the wrong files and cannot find all the >> files required. >> >> If you're feeling adventurous, I've found that you can do a binary patch >> by simply replacing the pattern 0x003a3b00 with 0x003b3b00 in >> mingw32-make.exe, and it should do the path splitting correctly and find >> the required files. >> >> Note that this is just a work-around, and Ruben will have to correct the >> way he cross-compiles the MinGW tools. >> >> See >> http://sourceforge.net/tracker/?func=detail&aid=3545000&group_id=202880&atid=983354 >> for details. > > Ahh thanks. > > But also jom fails, I thought jom could also handle mingw makefiles? No, Jom only handles NMake makefiles, afaik. -- .marius ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28.08.2012 19:27, marius.storm-ol...@nokia.com wrote: > On 28/08/2012 12:16, ext Peter Kümmel wrote: >> I've tried to build qtbase >> 1. on Windows 7 >> 2. rubenvb's mingw-w64: >> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/gcc-4.7-release/ >> 3. in Windows shell cmd.exe >> 4. as shadow build with ..\qtbase\configure.bat -fast -nomake demos -nomake >> examples -release >> >> It copies the headers and starts to build configure.exe but after compiling >> three files >> it starts to links and complains about missing .o files. >> >> Have I missed something or is building with mingw in cmd.exe not supported? > > This is not your fault, it's the rubenvb release which is broken, as the > GNU Make tool provided is not properly splitting the file paths. Thus, > mingw32-make is trying to stat the wrong files and cannot find all the > files required. > > If you're feeling adventurous, I've found that you can do a binary patch > by simply replacing the pattern 0x003a3b00 with 0x003b3b00 in > mingw32-make.exe, and it should do the path splitting correctly and find > the required files. > > Note that this is just a work-around, and Ruben will have to correct the > way he cross-compiles the MinGW tools. > > See > http://sourceforge.net/tracker/?func=detail&aid=3545000&group_id=202880&atid=983354 > for details. Ahh thanks. But also jom fails, I thought jom could also handle mingw makefiles? Peter ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] tools/configure with mingw build error
On 28/08/2012 12:16, ext Peter Kümmel wrote: > I've tried to build qtbase > 1. on Windows 7 > 2. rubenvb's mingw-w64: > http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/gcc-4.7-release/ > 3. in Windows shell cmd.exe > 4. as shadow build with ..\qtbase\configure.bat -fast -nomake demos -nomake > examples -release > > It copies the headers and starts to build configure.exe but after compiling > three files > it starts to links and complains about missing .o files. > > Have I missed something or is building with mingw in cmd.exe not supported? This is not your fault, it's the rubenvb release which is broken, as the GNU Make tool provided is not properly splitting the file paths. Thus, mingw32-make is trying to stat the wrong files and cannot find all the files required. If you're feeling adventurous, I've found that you can do a binary patch by simply replacing the pattern 0x003a3b00 with 0x003b3b00 in mingw32-make.exe, and it should do the path splitting correctly and find the required files. Note that this is just a work-around, and Ruben will have to correct the way he cross-compiles the MinGW tools. See http://sourceforge.net/tracker/?func=detail&aid=3545000&group_id=202880&atid=983354 for details. -- .marius ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
