pcs db's broken by 2 kdev instances?
apaku at gmx.de
Fri Aug 18 20:23:27 UTC 2006
On 18.08.06 14:28:48, Matt Rogers wrote:
> On Friday 18 August 2006 14:16, Andreas Pakulat wrote:
> > Hi,
> > asked this on IRC, got no replies. I'd like to know wether it is right
> > that running 2 instances of kdevelop at the same time, from different
> > compilation units (i.e. both 3.4 svn, but compiled at different times
> > and residing in different installation dirs) breaks the pcs db's? I
> > got the "pcs db's are invalid" dialog when started kdevelop after having
> > closed the 2 instances and a reboot in between.
> yes, it will, depending on how much time there is between the different
> versions. the pcs file version has been bumped at least twice since starting
> development on kdevelop 3.4
Well one is from the qmake4 branch right after the first merge into 3.4,
the other one is pretty up-to-date. So they're not more than 2 weeks
away from each other.
Don't get stuck in a closet -- wear yourself out.
More information about the KDevelop-devel