Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Plugins development => Topic started by: Guuestgulkan on June 25, 2014, 07:55:35 pm
-
This is on windows 7.
So I have Codeblocks release 13:12 (wxwidgets 2.8.12, Unicode, SDK version 1.19.0)
I am attempting to make a plugin.
I downloaded the source - ran the Codeblocks.cbp and ended up with a devel
directory conraining codeblocks import library and the codeblocks dll - and the share directory with
with the usual bundled plugins.
I went back to my codeblocks 13.12 - made the simple hello plugin (as described in the wiki)
and after some hassle got the hello.plugin file containing the hello.dll and the inner zipfile with the manifest.xml.
However, no I go the the plugin men and try to add the plugin, it obviously picks
the plugin file ok, but it always gives the error (on the yellow popup inforwindow)
"One or more plugins were not loaded.
This usually happens when a plugin is built for a different version of the sdk"
and it gives the name of the appropriate dll.
This always happens even if I try to trick the system by uninstalling an existing plugin (susch as the todo plugin)
and feeding it back.!!!
Any help/advice will be most appreciated
-
To compile a plugin targeting 13.12 you might not even need to compile C::B at all. There is a hint on the wiki how you link directly against the dll. This should always work. Except of that: what sources do you use exactly?
-
FYI: That message is a bug that was fixed in a nightly build.
Link to patch that fixes the message.
http://raw.githubusercontent.com/stahta01/cb_misc/master/Patches/applied/cb_src_fix_pluginmanager_install_error.patch (http://raw.githubusercontent.com/stahta01/cb_misc/master/Patches/applied/cb_src_fix_pluginmanager_install_error.patch)
Tim S.
-
I downloaded 13.12 windows binary from sourceforge (via this site).
I was using that to make a wizard - which went ok - then I though I'd try a plugin.
So I downlod 13.12.tar.gz again from sourceforge.
//** while I was typing this a reply came in --- I will try that fix **//
EDIT:
YES!
The cb_src_fix_pluginmanager_install_error.patch did the trick.
Thanks.