Code::Blocks Forums

User forums => Help => Topic started by: bgolding on January 10, 2008, 05:53:10 pm

Title: No plugins!
Post by: bgolding on January 10, 2008, 05:53:10 pm

I'm running C::B from SVN 4698, which I built on Redhat. This is my first time building from source.

The good news: the GUI starts up  :D
The bad news: Plugins->Manage Plugins shows an empty list. Obviously this restricts the usefulness somewhat.

I did
./configure --enable-static=yes --with-contrib-plugins=all --prefix=/blah/blah
make
make install

In my installation, I have:
codeblocks/share/codeblocks/plugins % ls
libastyle.a            libdebugger.a              libProfiler.a
libastyle.la*          libdebugger.la*            libProfiler.la*
libautosave.a          libdefaultmimehandler.a    libprojectsimporter.a
libautosave.la*        libdefaultmimehandler.la*  libprojectsimporter.la*
libbyogames.a          libdragscroll.a            libRegExTestbed.a
libbyogames.la*        libdragscroll.la*          libRegExTestbed.la*
libcb_koders.a         libenvvars.a               libscriptedwizard.a
libcb_koders.la*       libenvvars.la*             libscriptedwizard.la*
libclasswizard.a       libexporter.a              libSymTab.a
libclasswizard.la*     libexporter.la*            libSymTab.la*
libcodecompletion.a    libhelp_plugin.a           libtodo.a
libcodecompletion.la*  libhelp_plugin.la*         libtodo.la*
libcodesnippets.a      libkeybinder.a             libwxsmith.a
libcodesnippets.la*    libkeybinder.la*           libwxsmithcontribitems.a
libcodestat.a          liblib_finder.a            libwxsmithcontribitems.la*
libcodestat.la*        liblib_finder.la*          libwxsmith.la*
libcompiler.a          libopenfileslist.a
libcompiler.la*        libopenfileslist.la*

So why no plugins? Is there some very obvious build/setup step I am missing?

Title: Re: No plugins!
Post by: stahta01 on January 10, 2008, 09:50:17 pm

try it without the --enable-static=yes
Tim S

Title: Re: No plugins!
Post by: bgolding on January 11, 2008, 11:39:05 am

Tim, is this just a guess, or is there a reason you have suggested it? Because it seems to me that the plugins have been built OK and it is just a configuration problem.

I will try this suggestion, but it may take me some time and may cause other problems with my setup. I'll let you know if it works.

Title: Re: No plugins!
Post by: bgolding on January 14, 2008, 07:31:17 pm

I am now using shared libs
./configure --with-contrib-plugins=all --prefix=/blah/blah
and have built a clean version from SVN 4816, but the same problem persists.

These are the actual commands used to launch C::B (from a script in mybin dir)
LD_LIBRARY_PATH="/blah/blah/lib"
/blah/blah/bin/codeblocks

Is anyone able to advise me how C::B finds and loads plugins from the installation directory?

Title: Re: No plugins!
Post by: MortenMacFly on January 15, 2008, 07:52:08 am

Quote from: bgolding on January 14, 2008, 07:31:17 pm

Is anyone able to advise me how C::B finds and loads plugins from the installation directory?

Run the update script to complete the "compilation". This will create a launch script, too. BTW: You did a make install, did you?!

Title: Re: No plugins!
Post by: bgolding on January 15, 2008, 11:50:09 am

Morten,

I didn't run update (I assume you mean src/update from my trunk dir).

I was following these instructions: http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux)

So the build process was:
./bootstrap
./configure --with-contrib-plugins=all --prefix=/blah/blah
make
make install

When should I run update? Between make and make install? Perhaps you could review the Wiki page, it seems maybe it is out-of-date. The readme file BUILD in SVN doesn't mention update either.

Thanks, Ben

Title: Re: No plugins!
Post by: Jenna on January 15, 2008, 01:48:30 pm

I just tested it.
I removed my old C::B installation, to avoid side-effects, then I typed

Code

./configure --with-contrib-plugins=all --prefix=/home/jens/codeblocks-tmp
make
make install

in C::B's source-dir.

Now I can start C::B by typing

Code

/home/jens/codeblocks-tmp/bin/codeblocks

without setting LD_LIBRARY_PATH and C::B starts with all plugins.

Title: Re: No plugins!
Post by: bgolding on January 15, 2008, 03:24:04 pm

Jens, could you please try setting

Code

LD_LIBRARY_PATH=/home/jens/codeblocks-tmp/lib

and see whether that will prevent your plugins from loading correctly?

The problem I have is no root access --> I must set LD_LIBRARY_PATH to find libwx_gtk2u-2.8.so.0

Title: Re: No plugins!
Post by: Jenna on January 15, 2008, 04:04:55 pm

Quote from: bgolding on January 15, 2008, 03:24:04 pm

Jens, could you please try setting

Code

LD_LIBRARY_PATH=/home/jens/codeblocks-tmp/lib

and see whether that will prevent your plugins from loading correctly?

The problem I have is no root access --> I must set LD_LIBRARY_PATH to find libwx_gtk2u-2.8.so.0

It works the same way if I set LD_LIBRARY_PATH or not.
Where does your build looks for the plugin.
If C::B has started there should be two lines in the "Code::Blocks" tab in the logs where C::B tells you where it looks for plugins.

For me it looks like:

Code

Scanning for plugins in /home/jens/.codeblocks/share/codeblocks/plugins
Loaded 0 plugins
Scanning for plugins in /home/jens/codeblocks-tmp/share/codeblocks/plugins
Loaded 28 plugins

You can also start C::B with "-d" parameter and look in the debug-log if there are error-messages.

Is your wxWidgets installed in your home-dir or is it a global install.
Normally if everything is linked correct you don't need the LD_LIBRARY_PATH variable set.

You can look against which libraries C::B is linked by running

Code

ldd /path/to/codeblocks

Title: Re: No plugins!
Post by: Jenna on January 15, 2008, 04:24:29 pm

By the way:
afaik the plugins are loaded by C::B itself not by the OS, so they should not depend on LD_LIBRARY_PATH.

Title: Re: No plugins!
Post by: bgolding on January 15, 2008, 04:34:00 pm

According to the C::B tab, it's looking in the right place (the same dir I listed at the start of this thread).

Using -d parameter, no errors:

Code

Initialize EditColourSet .....
Initialize EditColourSet: done.
Loading toolbar...
Initializing plugins...

I have wxGTK which I built from source in my home dir. But actually I just copied libwx_gtk2u-2.8.so.0 (and the file it links to) into the /blah/blah/lib directory (which also contains libcodeblocks.a and .la). That is why I set LD_LIBRARY_PATH. See output of ld:

Code

ldd /blah/blah/bin/codeblocks
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xf6d15000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xf6ca8000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xf6c8e000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xf6c79000)
        libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0xf6c74000)
        libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0xf6c69000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xf6c33000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xf6bf6000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xf6bf3000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf6b78000)
        libwx_gtk2u-2.8.so.0 => /blah/blah/lib/libwx_gtk2u-2.8.so.0 (0xf6301000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xf62ef000)
        libdl.so.2 => /lib/libdl.so.2 (0xf62eb000)
        libm.so.6 => /lib/tls/libm.so.6 (0xf62c7000)
        libc.so.6 => /lib/tls/libc.so.6 (0xf619c000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xf60bd000)
        libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0xf60ba000)
        libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0xf60b2000)
        libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0xf60af000)
        libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0xf609c000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xf6035000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xf600f000)
        libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0xf6006000)
        libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0xf5ffe000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0xf5ff0000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xf5fc9000)
        libz.so.1 => /usr/lib/libz.so.1 (0xf5fb9000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xf5fb5000)
        libXxf86vm.so.1 => /usr/X11R6/lib/libXxf86vm.so.1 (0xf5fb0000)
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0xf5fa7000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0xf5f82000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xf5f64000)
        libtiff.so.3 => /usr/lib/libtiff.so.3 (0xf5f18000)
        libexpat.so.0 => /usr/lib/libexpat.so.0 (0xf5ef9000)
        /lib/ld-linux.so.2 (0xf6fe9000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6