[Development] Qt5 binary packages for testing

morten.sorvig at nokia.com morten.sorvig at nokia.com
Thu May 31 14:31:53 CEST 2012

On May 31, 2012, at 12:41 PM, ext simo.falt at nokia.com wrote:

> Moi,
> I made some modifications to binary package publishing scripts. Now it should be easier to file bug reports with correct sha1. All packages, both source and binary installers, are now stored to http://releases.qt-project.org/qt5.0/beta-snapshots/  ( old locations will remain for now)
> Build is triggered at 7 am and pm in case of new commits to qt5.git. Src packages will appear within 40 minutes and binary installers 3-5 hours after src packages. The progress can soon be followed via http://builds.qt-project.org/.
> In same directory there is also the sha1.txt containing sha1 and timestamp ( the timestamp is purely for CI usage, so please don't ask modifications to the format).
> Next steps are getting the Win builder back on track. It is failing at the moment, and it haven't generate new packages for a while. Also webkit seems to require some love and care.
> But for now, feel free to start testing.

Hi, testing on Mac OS X 10.7: 

- Package installs without error.
- However, rebuilding an example does not work due to a hardcoded buildbot path:

Mortens-MacBook-Pro:wiggly msorvig$ make qmake
/Users/builder/jenkins/workspace/qt5-beta-bin-osx/qt-everywhere-opensource-src-5.0.0/qtbase/bin/qmake -spec ../../../mkspecs/macx-clang -o Makefile wiggly.pro
make: /Users/builder/jenkins/workspace/qt5-beta-bin-osx/qt-everywhere-opensource-src-5.0.0/qtbase/bin/qmake: No such file or directory
make: *** [Makefile] Error 1

- I get a similar error when building en external project:

Mortens-MacBook-Pro:playground-desktopcomponents msorvig$ ../../QtSDK/Desktop/Qt/5.0.0/gcc/bin/qmake
WARNING: /Users/msorvig/QtSDK/Desktop/Qt/5.0.0/gcc/mkspecs/modules/qt_activeqt.pri:7: Unable to find file for inclusion /Users/builder/jenkins/workspace/qt5-beta-bin-osx/qt-everywhere-opensource-src-5.0.0/qtactiveqt/modules/qt_activeqt.pri

(etc for all modules)


More information about the Development mailing list