Review Request 108795: Perforce plugin for Kdevelop
Peter M. Clausen
petermichaelclausen at gmail.com
Tue Feb 5 22:49:35 UTC 2013
I wanted to test this, and it builds correctly as far as I can see:
$ ll $inst_path/install/lib/kde4/kdevperforce.so
-rw-r--r-- 1 clausen fedux 577K Feb 5 22:29
Then I've set
$ export KDEDIRS=$inst_path:KDEDIRS
I have set my P4CONFIG-variable and started
$ kdevelop 2> /tmp/kdev.err
But I cannot find any info that plugin is loaded, neither in
Plugin-Information nor in STDERR output. I have also tried to
$ export KDEDIRS=$inst_path:$inst_path/lib:$inst_path/lib/kde4:$KDEDIRS
Any suggestions? I'm sorry if this is the wrong place to post - if so point
me to the right place.
I also have some issues with UnitTest-plugin. Again, is the mailing-list
the place to post or somewhere else?
Thanks to everyone. I'm enjoying using Kdevelop. Perforce and
UnitTests-Plugin would ease my daily work if I get them going as I want to.
2013/2/5 Morten Volden <mvolden2 at gmail.com>
> This is an automatically generated e-mail. To reply, visit:
> Review request for KDevelop and Milian Wolff.
> By Morten Volden.
> *Updated Feb. 5, 2013, 7:36 p.m.*
> Description (updated)
> This plugin integrates KDevelop with the perforce command line client (p4). It currently supports: Add, Edit, Status, Annotate, History, Revert, Update and Commit and Diff.
> Source is here:
> or here:
> git clone git://anongit.kde.org/kdev-perforce
> The following use-cases are now unit-tested: Add Edit, Status, Annotate, History, Revert, Update(File), Update(Dir), Commit
> View Diff <http://git.reviewboard.kde.org/r/108795/diff/>
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel