[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: current state of using cmake to compile kdevelop
From: Sascha Cunz <sascha.cunz () tiscali ! de>
Date: 2005-05-09 15:16:17
Message-ID: 200505091716.18070.sascha.cunz () tiscali ! de
[Download RAW message or body]
Hi,
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
variables?
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
staticly?
Sascha
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic