Load custom plugin that isn't in the kdevelop tree

[René J.V. Bertin]

On Sunday April 12 2020 08:03:40 Πέτρος Σιλιγκούνας wrote:

>Building manually and installing kdevelop on /usr/local came along with all
>sorts of problems as it couldn't find the libcocoa.dylib for the
>QT_PLUGIN_PATH and messed up the original installation of brew.

For this kind of thing it *might* be easier to take inspiration on my officious MacPorts ports tree for KF5 which has patches for Qt that make it possible to install KF5 as if on Linux (or just install MacPorts with my tree for this development purpose).

>Can someone point me out how a plugin is tested before it actually moves
>into the kdevelop tree?

That would be a question for the -devel mailing list, but you could take the kdev-python, kdev-mercurial plugins as an example. Or, because your plugin is already part of the tree, do your development in a branch in which you merge upstream changes regularly. That way you probably won't have to worry about how it gets installed, only how to apply the HB build recipe to a git working copy instead of to what it would normally use.


Then of course you could install a Linux distro in a VM and work from there ... ;)

R.