On Tuesday 10 July 2007 5:09 pm, Giovanni Bajo wrote: > Hi Phil, > > currently, -e MODULE means "activate MODULE, checking that it's built in > Qt too".
No, it means "enable checks for MODULE", the default being "enable checks for all modules". > This is a little counter-intuitive to me: I would expect "-e > MODULE" to mean "I really really want MODULE to be there", and thus > configure.py to abort if the module(s) I specified are not built in Qt > and thus cannot be compiled. > > Do you instead consider the current behaviour better, or at least just > as potentially useful? If not, I will submit a patch to change it so > that configure.py fails if the module can't be activated. > > Otherwise, would you mind if I add a way to tell configure.py to abort > if the enabled modules can't be activated? I'd rather leave it as it is. Phil _______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
