current state of using cmake to compile kdevelop

Sascha Cunz sascha.cunz at
Mon May 9 17:02:04 UTC 2005

On Monday 09 May 2005 08:45, Sylvain Joyeux wrote:
> This is not for the KDevelop build itself, but for the developers which
> want to use its public interface

well, i think, i don't get your point here - because i think that it will not 
be posibile to do, what you're telling. At least not, if there are any static 
variables or objects.

For example: one plugin links a public interface library static and another 
one links against it's shared counterpart. Will both ever see the same static 

Though, i know kdevelop's interfaces do not use static members in classes. 
However DCOP skeletons and moc output does.

Having a kdevelop plugin that links staticly against any of kdevelop's 
interfaces, means that it has it's own static declaration of slots/signals. 
To my understanding, this will affect BC.

btw - would there be any real need to link the kdevelop public interfaces 


More information about the KDevelop-devel mailing list