[Qtscript-bindings] building on distros that split up the Qt package

Kent Hansen khansen at trolltech.com
Mon Aug 4 13:26:51 CEST 2008


Ian Monroe wrote:
> Qt4 has stopped being so atomic in some distros. Opensuse splits off
> QtWebKit4 into its own package. The result of this is documented at
> the bug I just submitted:
> https://bugzilla.novell.com/show_bug.cgi?id=413829
> Basically qconfig.h cannot be accurate, since the core of Qt might be
> compiled with QtWebKit off, and then QtWebkit is later compiled and
> packaged seperatedly.
>
> Writing the bug made me realize a solution for my problem. If you look
> at the macro from qconfig.h:
> #if defined(QT_NO_WEBKIT) && defined(QT_WEBKIT)
> # undef QT_NO_WEBKIT
> #elif !defined(QT_NO_WEBKIT) && !defined(QT_WEBKIT)
> # define QT_NO_WEBKIT
> #endif
>
> It appears that adding a -DQT_WEBKIT to the build would make sure that
> QT_NO_WEBKIT was never defined and hopefully the generator would go
> and do the right thing.
>
> However this isn't the case, even with  -DQT_WEBKIT the webkit files
> aren't generated.
>
> What mechanism decides what is generated or not?
>
> Ian
>   

Bindings are generated if the header that's input to the generator (by 
default qtscript_masterinclude.h) includes the relevant header file(s), 
and the typesystem file (by default build_all.txt) includes the relevant 
bindings definitions. If the C++ class declarations are not found you'll 
get "missing class definition" warnings.
Looks like QT_NO_WEBKIT is still defined. Commenting out the #ifndef 
QT_NO_WEBKIT in qtscript_masterinclude.h should verify that.

Kent



More information about the Qtscript-bindings mailing list