Thread-safety issue in cmake support ?

Milian Wolff mail at milianw.de
Mon Jun 7 16:57:27 UTC 2010


Christoph Cullmann, 07.06.2010:
> On Monday 07 June 2010 18:34:42 Andreas Pakulat wrote:
> > > Error occurs either in main thread or in plugin. When in main thread
> > > it raises from
> > > a slot execution which it turns call a method using introspection,
> > > making things difficult to investigate.
> > > 
> > > IMHO, a lock in CMakeUtils would be a possible solution.
> > 
> > Oh, or we could just drop KConfig usage and use QSettings for the project
> > files. After all we might have to get rid of kcm-usage for project-config
> > too. The only thing we'd loose is the ability to read from two files "at
> > the same time". But then again, maybe its even good that where stuff is
> > written is more explicit so we can more easily move things around...
> 
> QSettings ist not thread-safe, only reentrant.

Making the foreground lock look even better :)

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100607/596f82c9/attachment.sig>


More information about the KDevelop-devel mailing list