After doing a "make; make install" on OSX using the latest SVN and then running codeblocks from the installed bin directory, it's not finding any of the plugins.
Scanning for plugins in /Users/dkulp/Library/Application Support/codeblocks/share/codeblocks/plugins
Loaded 0 plugins
Scanning for plugins in /Users/dkulp/Applications/codeblocks/bin/../share/codeblocks
Loaded 0 plugins
The plugins are located in /Users/dkulp/Applications/codeblocks/lib/codeblocks/plugins so it looks like either the search path is wrong for OSX or the "make install" is putting them in the wrong location. I don't know the intent so not sure which is the proper fix.
Also note: the plugins all have ".so" extensions instead of the more normal .dylib extension on OSX.
Not sure what is the correct way to fix this. But I think it has been discussed in the forum. Please search about it.
I MacPorts we also patch the sources in order to find plugins. One of our developers added this:
but this is not fully portable and we would need to craft a better proposal for location of the plugins on Mac.
I'll test C::B on a macosx soon, so I'll see what I can do about this.
It might be nice to support this via a configure option (for both relative and absolute paths).
I've been using:
As it does two things:
1) Looks in the normal "unixy" directory structure
2) If it finds libcompiler.so, it searches for plugins named with .so instead of .dylib. When I run "make install", the plugins all are ending up as .so which wasn't being picked up due to the search of just .dylib. Searching for .so allows all the plugins to load.
An alternative could also be to change the build system to create dylib files on Mac rather than the so files.
The only way I was able to do that was to remove -module from all the Makefile.am files which would likely break everything else. That said, this is not an area i have any experience with. There is likely some automake flag or tool or something, but I have no idea.
As far as I can see here: http://stackoverflow.com/questions/2339679/what-are-the-differences-between-so-and-dylib-on-osx we're doing the right thing when we create the .so files. So this is better to be preserved. Are there any plugins that are .dylibs? If we have both .dylib and .so file we should change the build to produce just one of them.
They seem to all be .so files. wxSmith has some dyLibs, but they are then considered shared libs linked into the libwxsmith.so.
Yep, wxSmith uses some shared libs that are not plugins. So we're good to go with a .so only patch. Can you check what happens when you build cb from cb?
I would have no idea how to build anything from CB... I only use it for wxSmith. All real development is done in Xcode. That said, wxSmith in the new CB isn't really usable on my Macbook right now due to http://trac.wxwidgets.org/ticket/17302 Works fine on the non-retina external display.
With this patch:
and make on OSX 10.11.6 and move files to CodeBlocks.app I have:
Scanning for plugins in /Users/nnn/Library/Application Support/codeblocks/share/codeblocks/plugins
Loaded 0 plugins
Scanning for plugins in /Applications/CodeBlocks.app/Contents/Resources/share/codeblocks/plugins
^^^^^^^^
Loaded 55 plugins
Regards,
frankofrank
Last edit: Franko F 2016-11-16
Patch for extension .dylib for plugins on OSX:
and in every Makefile.am for plugin "nnn":
Last edit: Franko F 2016-11-16
Fixed in rev10930