Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Building CodeBlocks source
Jenna:
--- Quote from: sorinev on August 06, 2013, 10:19:53 pm ---Well yeah, I try not to. But when I get permission denied errors, I really don't know what the alternative is.
So I've got the IDE built, and the contrib plugins built, and I did the ./update, but the plugins don't seem to load when I start codeblocks? All the stuff present in my Windows version of the svn build is missing from my Linux svn build.
Jens' page seems to be saying that the contrib plugins can't be used on Ubuntu? Really?! :( I guess I don't really use them, but still...
--- End quote ---
I never wrote this.
You can use the contrib-plugins in ubuntu without any issues.
But you can not use the contrib-plugins-packages from my site, as ubuntu uses different lib-versions the debian does.
And I do not build ubuntu-packages.
I could do, but I personally don't like (and of course don't use) ubuntu (except for testing purposes) and I build packages for three versiond of fedora, two CentOS/RedHat versions and two debian versions (all in 32 and 64-bit) and this binds enough of my resources.
blauzahn:
If you see only the ubuntu-version, your compiled programm is either not installed or not started.
I have even uninstalled the ubuntu version of codeblocks to avoid conflicts. But before you start
uninstalling that, at least you can see, if you can start /usr/local/bin/codeblocks from the commandline.
If you still lack a sucessful installation, try only:
--- Code: ---make
--- End code ---
watch the result. And only when it looks ok (no error visible, instead: "Nothing to be done for `all-am'."), then enter:
--- Code: ---sudo make install
--- End code ---
If that does not work, check if you can write (as sudoer) to that directory at all. e.g.
--- Code: ---sudo install --directory /usr/local/include/codeblocks/scripting/sqplus
sudo touch /usr/local/include/codeblocks/scripting/sqplus/mytouchtest.txt
--- End code ---
sorinev:
I must have missed some part of the process somewhere then. The contrib plugins were successfully built, so I think there's some step I haven't done. I assumed I was supposed to run the ./update file? (which I did).
--- Code: ---output/share/codeblocks is full of all of the individual contrib zip files.
output/share/codeblocks/plugins is full of all the matching contrib .so files.
--- End code ---
sorinev:
--- Quote from: blauzahn on August 06, 2013, 10:57:01 pm ---at least you can see, if you can start /usr/local/bin/codeblocks from the commandline.
--- End quote ---
Yep, it starts ok from that directory the first try, just the contrib plugins are missing.
Jenna:
Do you use C::B to build C::B or do you use the automake-system ?
You wrote about both, if I remember correctly.
For automake you do not need the update-scripts.
Just (the simplest example):
* ./bootstrap
* ./configure --with-contrib-plugins=all
* make
* sudo make install
* codeblocks -v
Better would be:
* ./bootstrap
* mkdir build
* cd build
* -./configure --prefix=/home/username/whatever-you-like --with-contrib-plugins=all
* make -jx (where x is the amount of your cpu-cores+1)
* make install
* /home/username/whatever-you-like/bin/codeblocks -v
Both example assume you start from the root of C::B's sources.
The second one makes it easier to remove the whole build-tree, does not litter the sources with intermediate files and keeps your copy of C::B in a folder below your home-folder, so there can not be any access-right issues and you can keep multiple versions of C::B on one system (including "official" builds below /usr).
The -v parameter is not needed for normal use, but it gives more debug-messages if something went wrong, as it seems to be in your case.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version