User forums > Nightly builds

The 16 November 2013 build (9455) is out.

<< < (2/15) > >>

Jenna:

--- Quote from: oBFusCATed on November 17, 2013, 03:38:43 pm ---Check here: http://forums.codeblocks.org/index.php/topic,18528.msg126762.html#msg126762
Jens' packages are not compatible with ubuntu, probably you can read this on his page.

--- End quote ---
Partly correct.
I have packages from my repo installed on my 13.04 test vm without issues.

mariobarbara:

--- Quote from: oBFusCATed on November 17, 2013, 03:38:43 pm ---Check here: http://forums.codeblocks.org/index.php/topic,18528.msg126762.html#msg126762
Jens' packages are not compatible with ubuntu, probably you can read this on his page.

--- End quote ---

Thanks! I don't know why moore doesn't have his repos added to the codeblocks website...would be a hell of a lot easier for everyone.
Anyways jens' debian builds are working just fine for me, i'd switch to moore's but i noticed he doesn't give the actual build version name to his builds like jens (or i am missing the point...) because while jens' is named  "svn9453" and i KNOW it is a recent version, moore's is named "trunkbzr7726.lp" which i don't really know what it stands for....

dmoore:

--- Quote from: mariobarbara on November 17, 2013, 04:24:51 pm ---Thanks! I don't know why moore doesn't have his repos added to the codeblocks website...

--- End quote ---

because of annoying issues like:


--- Quote ---but i noticed he doesn't give the actual build version name to his builds like jens (or i am missing the point...) because while jens' is named  "svn9453" and i KNOW it is a recent version, moore's is named "trunkbzr7726.lp" which i don't really know what it stands for....

--- End quote ---

I am using Launchpad's automated build service, which only works with bzr repos. The bzr repo that the packages are created from is here: https://code.launchpad.net/~damien-moore/codeblocks/nightly
Eventually I should be able to use the SVN repo number in the package name, but Ubuntu's build servers don't support this yet.

Code::Blocks itself will still show the actual SVN revision number that the build is based on in the splash screen and the about page.

dmoore:
Updated Ubuntu packages (i386 + AMD64 for Precise through Trusty) will soon be available here.


--- Code: ---sudo add-apt-repository ppa:damien-moore/codeblocks-nightly
sudo apt-get update
sudo apt-get install codeblocks codeblocks-contrib

--- End code ---

Note: If you are using Code::Blocks from Pasgui's repository you will need to uninstall it and disable that repo before adding this one and reinstalling.

Workaround for possible crash related to compiler plugin at start up:
1. Open terminal, run "codeblocks --safe-mode"
2. Plugins -> Manage Plugins -> Compiler plugin -> Enable, then close the dialog
3. Accept all prompts
4. Close codeblocks
5. Start codeblocks as you normally would and everything should work normally.

cacb:

--- Quote from: mariobarbara on November 17, 2013, 04:24:51 pm ---
--- Quote from: oBFusCATed on November 17, 2013, 03:38:43 pm ---Check here: http://forums.codeblocks.org/index.php/topic,18528.msg126762.html#msg126762
Jens' packages are not compatible with ubuntu, probably you can read this on his page.

--- End quote ---

Thanks! I don't know why moore doesn't have his repos added to the codeblocks website...would be a hell of a lot easier for everyone.
Anyways jens' debian builds are working just fine for me, i'd switch to moore's but i noticed he doesn't give the actual build version name to his builds like jens (or i am missing the point...) because while jens' is named  "svn9453" and i KNOW it is a recent version, moore's is named "trunkbzr7726.lp" which i don't really know what it stands for....

--- End quote ---

I use Kubuntu and build C::B myself using Jens' preconfigured tarball source here
http://apt.jenslody.de/testing/pool/main/c/codeblocks/  (download filename *.orig.tar.gz)

HOWTO
1. download *.orig.tar.gz as explained above
2. Expand in folder with full ownership (I tend to get problems with e.g. Windows NTFS partitions, so use ext3/ext4 instead)
3. If you have special build of wxWidgets 2.8.12 like me, build against the official Kubuntu repository version. You may have to edit the debian/rules file in the expanded files, and add the option shown in red

--- Quote ---DEB_CONFIGURE_EXTRA_FLAGS=--with-contrib-plugins=all  --with-wx-config=/usr/bin/wx-config --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info

--- End quote ---

4. Then just do

--- Code: ---$ sudo dpkg-buildpackage
--- End code ---

the result is a collection of .deb files. The svn number changes every time, but for 9099 the installation was done like this

--- Code: ---$ sudo dpkg -i codeblocks-common_12.11svn9099_all.deb
$ sudo dpkg -i libcodeblocks0_12.11svn9099_i386.deb
$ sudo dpkg -i libwxsmithlib0_12.11svn9099_i386.deb
$ sudo dpkg -i codeblocks_12.11svn9099_i386.deb
$ sudo dpkg -i codeblocks-contrib-common_12.11svn9099_all.deb
$ sudo dpkg -i codeblocks-libwxcontrib0_12.11svn9099_i386.deb
$ sudo dpkg -i codeblocks-contrib_12.11svn9099_i386.deb
--- End code ---

When upgrading, I typically get some warnings the first time this script is executed. By running the script one more time, all is fine.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version