The new Release 20.03 is out! You can download binaries for Windows and many major Linux distros here .
be careful with the cases, see somewhere a sticky post of mine in the forums, on what to do for plug-ins and their CamelCase-d names, aswell as manifest files, makefiles, etc ...EDIT : http://forums.codeblocks.org/index.php/topic,4290.0.html
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><CodeBlocks_plugin_manifest_file> <SdkVersion major="1" minor="11" release="11" /> <Plugin name="libbrowsetracker.so"> <Value title="browsetracker" /> <Value version="0.1" /> <Value description="Browse to previous source positions" /> <Value author="Pecan Heber" /> <Value authorEmail="" /> <Value authorWebsite="" /> <Value thanksTo="" /> <Value license="GPL" /> </Plugin></CodeBlocks_plugin_manifest_file>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><CodeBlocks_plugin_manifest_file> <SdkVersion major="1" minor="11" release="11" /> <Plugin name="browsetracker"> <Value title="browsetracker" /> <Value version="0.1" /> <Value description="Browse to previous source positions" /> <Value author="Pecan Heber" /> <Value authorEmail="" /> <Value authorWebsite="" /> <Value thanksTo="" /> <Value license="GPL" /> </Plugin></CodeBlocks_plugin_manifest_file>
it's because the plugin is called browsetracker. C::B will get load the file browsetracker.so/.dll when it is loading the plugin. It should have the same name as de .cbplugin file
that is what I was trying to say.. the name of the .so file should be the same as the name of the .cbplugin file so if you don't want to use the lib at front of the plugin name, don't link it that way.
how do the other plugins do this ?compiler, debugger, keybinder, copystrings, ... ?do they do the same trick ??Sorry I don't have time to help investigate, doing nightly live tests in a tunnel in France ;-)