On Thursday, December 15, 2011 11:06:47 you wrote: > On Monday 12 December 2011 15:21:40 Stephen Kelly wrote: > > Hi there, > > > > Is there any plan to keep or remove the defines in features.txt in Qt 5? > > (eg, QT_NO_SQL, QT_NO_DATESTRING etc) > > > > A colleague told me about talk of removing all the ifdefs, but he > > thought > > he'd convinced whoever it was he was talking to that the stuff should be > > kept. > > > > Is it something that would need to be modularised? > > There is the feature that are disabled in the boostrapping phase. Thos might > stay. > > For the other ones: The policy in Qt 4 was that we do not maintain them, but > we leave them there (as they do not hurt in most cases) and accept patches > that fix them. > I don't see why we should change that.
Nor do I. We've certainly had cases where it was useful to have them there. The reason I'm bringing it up is that I want to be able to communicate through the CMake files which features Qt was built excluding. For example, if Qt was built with QT_NO_DATESTRING, it makes sense for all downstreams to define QT_NO_DATESTRING too. Obviously I don't want to do that work if there is a plan to remove the features and the ifdefs themselves. If the plan is not to remove them, then I can go ahead with the work. Thanks, -- Stephen Kelly <step...@kdab.com> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development