Hi,
I've been trying to install the codeblocks nightly on my machine (Fedora 12 64-bit) but have been running into some difficulties. I can get the main program to install without any errors and can run the program fine, but I can't get any of the plugins to work. Here's how I installed it:
svn checkout svn://svn.berlios.de/codeblocks/trunk
./bootstrap
./configure --with-contrib-plugins=all
make
sudo make install
I also looked in /usr/lib64/codeblocks/plugins and it's empty.
Is there something I'm missing? I've searched around and haven't found anything that works.
Thanks,
Matt
Quote from: Liv-Z on February 12, 2010, 06:43:35 AM
Hi,
I've been trying to install the codeblocks nightly on my machine (Fedora 12 64-bit) but have been running into some difficulties. I can get the main program to install without any errors and can run the program fine, but I can't get any of the plugins to work. Here's how I installed it:
svn checkout svn://svn.berlios.de/codeblocks/trunk
./bootstrap
./configure --with-contrib-plugins=all
make
sudo make install
I also looked in /usr/lib64/codeblocks/plugins and it's empty.
Is there something I'm missing? I've searched around and haven't found anything that works.
Thanks,
Matt
If you configure it without using the
--prefix parameter the installation will not be directly below
/usr but below
/usr/local (or whatever your distro uses as default for user-compiled software).
If you have had an installation directly below
/usr (e.g. from a repo or configured with
--prefix=/usr), this might interfer.
Do you get any error messages, if you start C::B in a console window ?
Thanks for the reply.
Quote from: jens on February 12, 2010, 07:21:11 AM
If you configure it without using the --prefix parameter the installation will not be directly below /usr but below /usr/local (or whatever your distro uses as default for user-compiled software).
If you have had an installation directly below /usr (e.g. from a repo or configured with --prefix=/usr), this might interfer.
Yea, all of the plugin files are present in the /usr/local/lib/codeblocks/plugins directory. I have previously installed both from a repo and using the --prefix configuration, but uninstalled everything afterwards. Do you think these would still be causing problems, even after uninstalling?
Quote from: jens on February 12, 2010, 07:21:11 AM
Do you get any error messages, if you start C::B in a console window ?
No, I don't get any error messages.
Quote from: Liv-Z on February 12, 2010, 08:34:24 AM
Do you think these would still be causing problems, even after uninstalling?
Not sure, I use several C::B installations for testing purposes under my home-directory and it works.
Nevertheless, you can try what happens if you remove the empty (or no longer used) C::B directories in the systems standard paths, like
/usr/lib[32|64]/codeblocks,
/usr/share/codeblocks, and make sure that no libs or binaries of C::B remain in
/usr/bin or
/usr/lib[32|64].
You can also start C::B and copy and paste the content of the "Code::Blocks"-tab in the "Logs & others"-pane.
We should see where it searches for lexers and plugins there.
I checked the log and C::B was looking in /usr/local/lib64 for plugins, which was empty in my case. I copied over the files stored in /usr/local/lib and now everything seems to be working fine.
Thanks again for all of your help!