[Releasing] Alpha package ready for testing

[Thiago Macieira]

On sexta-feira, 30 de março de 2012 12.25.16, marius.storm-olsen at nokia.com 
wrote:
> Hi,
> 
> Another package is ready for testing at
>    
> http://releases.qt-project.org/alpha/20120330/qt-everywhere-opensource-src-
> 5.0.0-alpha.tar.gz or
>    
> http://releases.qt-project.org/alpha/20120330/qt-everywhere-opensource-src-
> 5.0.0-alpha.zip
> 
> This package contains an additional fix for building WebKit on OSX, so lets
> hope this is final.
> 
> Please test.

Same error as yesterday:

Reading /tmp/qt-everywhere-opensource-src-5.0.0/qtwebkit-examples-and-
demos/examples/examples.pro
 Reading /tmp/qt-everywhere-opensource-src-5.0.0/qtwebkit-examples-and-
demos/examples/browser/browser.pro
Project MESSAGE: Warning: unknown QT module: webkit
[...]

In file included from main.cpp:42:0:
window.h:46:23: fatal error: QWebElement: No such file or directory
gmake[3]: *** [.obj/debug-shared/main.o] Error 1
gmake[3]: Leaving directory `/tmp/qt-everywhere-opensource-src-5.0.0/qtwebkit-
examples-and-demos/examples/webkit/domtraversal'

Configure line:
./configure -prefix /tmp/qt5inst -opensource -confirm-license -fast -developer-
build -nomake tests

Trying again:
$ cd /tmp/qt-everywhere-opensource-src-5.0.0/qtwebkit-examples-and-
demos/examples/webkit/domtraversal 

$ /tmp/qt5inst/bin/qmake 
Project MESSAGE: Warning: unknown QT module: webkit

$ ls -l /tmp/qt5inst/mkspecs/modules/qt_webkit.pri
-rw-r--r--. 1 thiago thiago 1908 Mar 30 08:59 
/tmp/qt5inst/mkspecs/modules/qt_webkit.pri

It's failing here (qt.prf):
for(QTLIB, QT) {
    QTLIBNAME = $$eval(QT.$${QTLIB}.name)
    isEmpty(QTLIBNAME) {
        message("Warning: unknown QT module: $$QTLIB")
        next()
    }

Debug:
DEBUG 2: Project Parser [var replace]: QT.$${QTLIB}.name -> QTLIB
DEBUG 1: Running project expand: eval(QT.webkit.name) [6]

But it's set in qt_webkit.prf:
QT.webkit.name = QtWebKit

So my conclusion is that the qt_webkit.prf file was not loaded.

Searching for where they might be loaded, I think I found it in qt_config.prf:
   for(dir, $$list($$unique($$list($$replace($$list($$dirname(QMAKE_QT_CONFIG) 
\
                                                    $$replace($$list($$split($$list($$(QMAKEPATH)), 
$$DIRLIST_SEPARATOR)), 
$, /mkspecs)), \
                                             $, /modules) \
                                   $$QMAKE_EXTRA_MODULE_FORWARDS)))) {
      debug(1, "Loading modules from $${dir}")
      for(mod, $$list($$files($$dir/qt_*.pri))) {
         # For installed Qt these paths will be common for all modules
         # For development these will vary per module, and syncqt will 
override the value in the
         # qt_<module>.pri forwarding file
         QT_MODULE_INCLUDE_BASE = $$[QT_INSTALL_HEADERS]
         QT_MODULE_LIB_BASE = $$[QT_INSTALL_LIBS]
         QT_MODULE_PLUGIN_BASE = $$[QT_INSTALL_PLUGINS]
         QT_MODULE_BIN_BASE = $$[QT_INSTALL_BINS]
         QT_MODULE_IMPORT_BASE = $$[QT_INSTALL_IMPORTS]
         include($$mod)
      }
   }

Searching for that debug-1 statement shows:
DEBUG 1: Project DEBUG: Loading modules from /tmp/qt-everywhere-opensource-
src-5.0.0/qtbase/mkspecs/modules

That is, the *installed* qmake is searching for the .prf files in the *build* 
location. That directory is empty.



-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20120330/f3ace9b3/attachment.sig>