John Levon wrote: > On Fri, Dec 27, 2002 at 04:08:44PM +0100, Alfredo Braunstein wrote: > >> >This is not a bug > > Hrrm.
Indeed. > >> and the a.unlock() is a safe and appropriate method to > > Is unlock() a no-op on non-thread Qt ? unlock() is declared inside an #ifdef QT_THREAD_SUPPORT on qapplication.h. How is it supposed to work? Is there a way to get these qt compilation flags? (in fact, I think that they must coincide exactly with the ones used for compiling qt). Must they be detected in configure? Btw, Redhat rpms from kde.org have thread support compiled in. > > If not we need an #ifdef > > john > Confused, Alfredo
