On Fri, Aug 26, 2011 at 11:53:26AM +0000, ext [email protected] wrote: > > Ben wrote: > > +1 > > It seems to match how Qt4 works quite well too, so it should make it easy > > to transition to Qt5. > > A further simplification proposed by Thomas and Lars was to use a MODULE tag > in the .pro file for all modules that are qmake based or handled (so you > don't have to add them to LIBS): > > MODULE += qtwebkit qtpim some_module_that_doesnt_start_with_qt > > This would be a little different from Qt4, but nice and simple. > we can do this renaming, but to make it really symmetrical in all directions would mean quite some replacing in the existing .prf and module/*.pri files. not a big deal per se ...
the problem of optional modules is already kind of solved - just check whether QT_CONFIG contains the module you want. a purely declarative way via a separate variable like OPTIONAL_MODULES seems to make sense, but it doesn't fit particularly well with the way how qmake works (setting conditionals on the presence of the module within the project file would be asymmetrical). _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
