ThreadSearch and Lib Finder plugins depend on wxSmith plugin to install correctly.
If wxSmith plugin is not installed (not selected during installation), then ThreadSearch/Lib Finder plugin will fail to load every time Code::Blocks start.
The error message is:
Warning
One or more plugins were not loaded. This usually happens when a plugin is built for a different version of the Code::Blocks SDK. Check the application log for more info.
List of failed plugins:
lib_finder.dll
ThreadSearch.dll
They do not appear in Plugins > Manage plugins list.
However, if wxSmith was installed, then they load correctly. Even after removing wxSmith plugins from Plugins > Manage plugins list later, they continue to load and work normally.
Code::Blocks 13.12 (codeblocks-13.12mingw-setup.exe) on Windows 7 64-bit
I don't have this issue on my WinXP, can you try to test a clean latest nightly version of C::B.
I Think the problem is with the installer and not Code::Blocks. I believe the installer mess up the configuration for some plugins (Lib Finder and ThreadSearch) if wxSmith plugin is not installed.
I tested the nightly build (10035) which runs fine as it does not have the installer. Also, it comes with all the plugins.
To reproduce:
Now, every time C::B load, it will not be able to load Lib Finder and ThreadSearch plugins.
This happens probably because if you don't install the wxsmith plugin, the one of the dlls is not installed, too. These dll is used by both libfinder and thread search plugins.
This is just a guess, I've not tried it as I don't run windows.
Last edit: Teodor Petrov 2014-11-24
Hi, Teodor Petrov(OBF), your guess is correct. I'm not familiar with the install script, but I just look at the file: http://cb.biplab.in/websvn/filedetails.php?repname=codeblocks&path=%2Fsetup%2Fsetup.nsi, I see that it has some section like:
I also see that the file "ThreadSearch.dll" depends on the file "wxcustombutton.dll", so if wxSmith is not installed, the ThreadSearch plugin will not load correctly.
This bug is confirmed, but we are waiting some setup script exports to fix them.
@Morten: Do you think this could be solved easily?