Code::Blocks - User contributions [en]

Installing Code::Blocks from source on Gentoo

2006-09-13T01:24:50Z

Crzysdrs: /* Subversion Portage Overlay */

== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
The current suggested method for emerging Code::Blocks is through the use of custom Ebuilds. The most prominently known portage overlay for the ebuilds is located here: [http://forums.gentoo.org/viewtopic-t-440412.html Gentoo Forums Code::Blocks Portage Overlay]

To create an overlay, please read [http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

=== Create your own overlay ===
Another method of pulling together your own Ebuilds and creating your own portage overlay is to view the bug report for adding Code::Blocks to portage. [http://bugs.gentoo.org/show_bug.cgi?id=89533 Gentoo Code::Blocks Package Suggestion]

== Preparing Code::Blocks from Source (For 1.0rc2) ==

'''WORK IN PROGRESS'''

( Note: This is non-official and unverified. It worked for me, but... )

===Prepare Libraries===

Code::Blocks uses the wxWidgets (http://www.wxwindows.org/) library for its GUI. wxWidgets in turn uses GTK+ (http://www.gtk.org/). GTK+ is the library which GNOME desktop uses, but GNOME is not required to use it. In fact, odds are very good that if you have a number of GUI programs installed, you already have it. wxWidgets is also very common, if slightly less so.

You need to compile the wxGTK package with the following use flag:

+gtk2

The best way of getting this done is by adding a line to /etc/portage/package.use and recompiling wxGTK :

# echo x11-libs/wxGTK gtk2 >> /etc/portage/package.use
# emerge wxGTK

Note: Code::Blocks now works fine with Unicode. So you might want to build wxGTK with +unicode flag.

===Get the source code===

For this you have 2 options:

====Option 1: Download a source tarball.====

This is easy and means you have an easily-reproduced source set.

1) '''Download a source tarball''' from [http://sourceforge.net/project/showfiles.php?group_id=126998&package_id=142469 The Download Section of CodeBlocks.org]

2) '''Extract it'''. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however. This should create a codeblocks-1.0rc2 ( or similar ) folder.

====Option 2: Fetch from CVS====

This is not signifigantly harder and means you have a more up-to-date version of the source code. Usually this means more features and different bugs, which might be more or less annoying.

1) '''Install the CVS client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/cvs

2) '''Set the CVS root'''. Run the following command, and enter the password ''anonymous'' when asked :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login
Note that simply hitting enter--not entering a password--might also work.

3) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that CVS will create a codeblocks directory for you. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however.
# cd /usr/local/src
The following command fetches the source from the CVS server :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks checkout codeblocks

===Compile the Code===

1) '''cd to codeblocks directory'''. Following our example, from CVS this would be /usr/local/src/codeblocks; from a tarball, something like /usr/local/src/codeblocks-1.0rc2 :
# cd /usr/local/src/codeblocks
or
# cd /usr/local/src/codeblocks-1.0rc2

2) '''bootstrap'''. The very first time you unpack the source (or checkout from CVS), you need to run ./bootstrap. This will create a sane building environment.
# ./bootstrap
Note: If you get weird errors here try running following command and then bootstrap again.
# find . -type f -and -not -name "*.cpp" -and -not -name "*.h" -and -not -name "*.png" -and -not -name "*.bmp" | sed "s/.*/\"\\0\"/" | xargs dos2unix

3) '''configure'''. Use 'configure --help' to see what things you can enable or disable.
# ./configure

4) '''make and make install'''.
# make
# sudo make install

===More===

to come

To run Code::Blocks:
# codeblocks

===References===

[https://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&t=29 Linux releases or compiling on Linux] from the forum

[http://sourceforge.net/cvs/?group_id=126998 Code::Blocks : CVS access instructions]

[http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services]

===Credits===

Original Author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )

Installing Code::Blocks from source on Linux

2006-09-12T17:33:50Z

Crzysdrs: /* Building Code::Blocks RC2 and SVN */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]
These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.6.1 or later) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

You do not need to Compile wxWidgets if your distribution has wxGTK 2.6 and wxGTK 2.6-dev package available. A quick search for "wxGTK" through your respective package manager should show bring up the needed packages. After you have installed successfully you can moving on the the Installing Code::Blocks portion. If you are using Ubuntu and have installed the wxGTK package, you must also have the dev version as well as the "wx-common" package in order to successfully compile Code::Blocks.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK installation===

====Getting wxGTK====

Visit the [http://www.wxwidgets.org wxWidgets web site]. Click the "Download" button at the top of the page. Under wxWidgets 2.6.3 downloads, select wxGTK. Save the file in <tt>~/devel</tt>.

wxWidgets project has released two patches for 2.6.3 release. Click the "Patches" in the left side of the page. Download the Patch 2, either in zip or tar.gz format. Save the file in <tt>~/devel</tt>

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.6.3.tar.gz</pre>

Move the patch to the wxGTK directory

<pre>mv wxWidgets-2.6.3-Patch-2.tar.gz wxGTK-2.6.3</pre>

or

<pre>mv wxWidgets-2.6.3-Patch-2.zip wxGTK-2.6.3</pre>

Switch to the wxGTK directory

<pre>cd wxGTK-2.6.3</pre>

Extract the patch

<pre>tar zxf wxWidgets-2.6.3-Patch-2.tar.gz</pre>

or

<pre>unzip -fo wxWidgets-2.6.3-Patch-2.zip</pre>

Remove the patch file

<pre>rm wxWidgets-2.6.3-Patch-2.tar.gz</pre>

or

<pre>rm wxWidgets-2.6.3-Patch-2.zip</pre>

====wxWidgets build====

Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

(Note: it's not necessary to make or install stc if you're compiling cvs HEAD or Code::Blocks newer than RC1)

Add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile)
(On Suse 10.1 edit /etc/profile.local, it will only be available after a new login). an example PATH
export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH

'''Note:''' On Ubuntu Hoary it was necessary to check "Run command as login shell"
in the gnome-terminal profile-settings, otherwise the PATH changes are not available in a gnome-terminal window.

add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)
then run:
ldconfig
source /etc/profile

That's it. Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.6
wx-config --libs
which should have at least
-L/opt/wx/2.6/lib -lwx_gtk2-2.6
but can contain other flags as well.
which wx-config
should return /opt/wx/2.6/bin/wx-config

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the SVN repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0rc2 source code (tarball)" codeblocks-1.0rc2.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0rc2.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0rc2</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0rc2</pre>

=====Getting the latest sources from SVN=====
'''IMPORTANT NOTICE: The Sourceforge CVS is no longer used although it still exists'''

Enter your development directory:
<pre>cd ~/devel</pre>

Then checkout the source using one of [https://www.codeblocks.org/source_code.shtml these] methods.

This will create the directory <tt>trunk</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd trunk</pre>

====Building Code::Blocks RC2 and SVN====
If you are a Gentoo user, please see [[Compiling_Code::Blocks_in_Gentoo]].

If you're compiling the svn trunk versions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks as follows:

./bootstrap

This sets up the configure script and it's dependencies. It only needs to be run once (after downloading the source from svn). '''If you get errors like:'''
aclocal:configure.in:61: warning: macro `AM_OPTIONS_WXCONFIG' not found in library
Then aclocal is having trouble finding the wxWidgets .m4 files. You can do one of two things:
To just get bootstrap to find the path this time do:

<pre>export ACLOCAL_FLAGS="-I `wx-config --prefix`/share/aclocal"</pre> 

To change the aclocal search path more permanently do:
echo `wx-config --prefix`/share/aclocal >> /usr/share/aclocal/dirlist
Then aclocal will also search somewhere like /opt/wx/2.6/share/aclocal

(*Note// '''If you run ./bootstrap and get errors like''':
: bad interpreter: File not found
then there exists a problem with DOS line-endings. i had this error after i tried to build a codeblocks from sources which were checked out with cvs on a windows machine. After i checked out a fresh copy of codeblocks from cvs under Ubuntu linux (see above topic: Downloading the latest source package fom SVN), all errors were gone.
//tiwag 051008*) 
Or, instead of downloading from CVS, you might consider using the little command line tool dos2unix, which normally comes with most distributions. //lizzarddude060103
 
If configure aborts with some unspecific error message(".infig.status: error: cannot find input file: Makefile"), you might consider also running
dos2unix bootstrap acinclude.m4 codeblocks.pc.in configure.in Makefile.am
before running bootstrap

Once you've run the bootstrap script, installing is as simple as:
./configure
make
make install

To uninstall you can later run:
make uninstall

If you want to recompile everything, first run:
make clean
and then follow the above sequence for installing.

By default, CodeBlocks will install to /usr/local. If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:
./configure --prefix=/opt/codeblocks-svn
or similar. Then you can later install a different build like:
./configure --prefix=/opt/codeblocks2-svn
followed by 'make && make install' as usual.

By default, CodeBlocks will not compile the contributed plugins from SVN. If you want to compile / install them too, replace the above ./configure command with:
./configure --enable-contrib
followed by 'make && make install' as usual.

To see a list of other options available for configuring the build of CodeBlocks do:
./configure --help

To compile under gentoo, use
./configure --with-wx-config=wx-config-2.6

====Building Code::Blocks RC1 and former====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

Installing Code::Blocks from source on Gentoo

2006-09-12T17:29:19Z

Crzysdrs:

== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
The current suggested method for emerging Code::Blocks is through the use of custom Ebuilds. The most prominently known portage overlay for the ebuilds is located here: [http://forums.gentoo.org/viewtopic-t-440412.html Gentoo Forums Code::Blocks Portage Overlay]

=== Create your own overlay ===
Another method of pulling together your own Ebuilds and creating your own portage overlay is to view the bug report for adding Code::Blocks to portage. [http://bugs.gentoo.org/show_bug.cgi?id=89533 Gentoo Code::Blocks Package Suggestion]

== Preparing Code::Blocks from Source (For 1.0rc2) ==

'''WORK IN PROGRESS'''

( Note: This is non-official and unverified. It worked for me, but... )

===Prepare Libraries===

Code::Blocks uses the wxWidgets (http://www.wxwindows.org/) library for its GUI. wxWidgets in turn uses GTK+ (http://www.gtk.org/). GTK+ is the library which GNOME desktop uses, but GNOME is not required to use it. In fact, odds are very good that if you have a number of GUI programs installed, you already have it. wxWidgets is also very common, if slightly less so.

You need to compile the wxGTK package with the following use flag:

+gtk2

The best way of getting this done is by adding a line to /etc/portage/package.use and recompiling wxGTK :

# echo x11-libs/wxGTK gtk2 >> /etc/portage/package.use
# emerge wxGTK

Note: Code::Blocks now works fine with Unicode. So you might want to build wxGTK with +unicode flag.

===Get the source code===

For this you have 2 options:

====Option 1: Download a source tarball.====

This is easy and means you have an easily-reproduced source set.

1) '''Download a source tarball''' from [http://sourceforge.net/project/showfiles.php?group_id=126998&package_id=142469 The Download Section of CodeBlocks.org]

2) '''Extract it'''. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however. This should create a codeblocks-1.0rc2 ( or similar ) folder.

====Option 2: Fetch from CVS====

This is not signifigantly harder and means you have a more up-to-date version of the source code. Usually this means more features and different bugs, which might be more or less annoying.

1) '''Install the CVS client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/cvs

2) '''Set the CVS root'''. Run the following command, and enter the password ''anonymous'' when asked :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login
Note that simply hitting enter--not entering a password--might also work.

3) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that CVS will create a codeblocks directory for you. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however.
# cd /usr/local/src
The following command fetches the source from the CVS server :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks checkout codeblocks

===Compile the Code===

1) '''cd to codeblocks directory'''. Following our example, from CVS this would be /usr/local/src/codeblocks; from a tarball, something like /usr/local/src/codeblocks-1.0rc2 :
# cd /usr/local/src/codeblocks
or
# cd /usr/local/src/codeblocks-1.0rc2

2) '''bootstrap'''. The very first time you unpack the source (or checkout from CVS), you need to run ./bootstrap. This will create a sane building environment.
# ./bootstrap
Note: If you get weird errors here try running following command and then bootstrap again.
# find . -type f -and -not -name "*.cpp" -and -not -name "*.h" -and -not -name "*.png" -and -not -name "*.bmp" | sed "s/.*/\"\\0\"/" | xargs dos2unix

3) '''configure'''. Use 'configure --help' to see what things you can enable or disable.
# ./configure

4) '''make and make install'''.
# make
# sudo make install

===More===

to come

To run Code::Blocks:
# codeblocks

===References===

[https://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&t=29 Linux releases or compiling on Linux] from the forum

[http://sourceforge.net/cvs/?group_id=126998 Code::Blocks : CVS access instructions]

[http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services]

===Credits===

Original Author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )

Installing Code::Blocks from source on Gentoo

2006-09-12T17:28:14Z

Crzysdrs: /* Preparing Code::Blocks from Source (Outdated) */

{{outdated}}
[[Category:Outdated]]

== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
The current suggested method for emerging Code::Blocks is through the use of custom Ebuilds. The most prominently known portage overlay for the ebuilds is located here: [http://forums.gentoo.org/viewtopic-t-440412.html Gentoo Forums Code::Blocks Portage Overlay]

=== Create your own overlay ===
Another method of pulling together your own Ebuilds and creating your own portage overlay is to view the bug report for adding Code::Blocks to portage. [http://bugs.gentoo.org/show_bug.cgi?id=89533 Gentoo Code::Blocks Package Suggestion]

== Preparing Code::Blocks from Source (For 1.0rc2) ==

'''WORK IN PROGRESS'''

( Note: This is non-official and unverified. It worked for me, but... )

===Prepare Libraries===

Code::Blocks uses the wxWidgets (http://www.wxwindows.org/) library for its GUI. wxWidgets in turn uses GTK+ (http://www.gtk.org/). GTK+ is the library which GNOME desktop uses, but GNOME is not required to use it. In fact, odds are very good that if you have a number of GUI programs installed, you already have it. wxWidgets is also very common, if slightly less so.

You need to compile the wxGTK package with the following use flag:

+gtk2

The best way of getting this done is by adding a line to /etc/portage/package.use and recompiling wxGTK :

# echo x11-libs/wxGTK gtk2 >> /etc/portage/package.use
# emerge wxGTK

Note: Code::Blocks now works fine with Unicode. So you might want to build wxGTK with +unicode flag.

===Get the source code===

For this you have 2 options:

====Option 1: Download a source tarball.====

This is easy and means you have an easily-reproduced source set.

1) '''Download a source tarball''' from [http://sourceforge.net/project/showfiles.php?group_id=126998&package_id=142469 The Download Section of CodeBlocks.org]

2) '''Extract it'''. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however. This should create a codeblocks-1.0rc2 ( or similar ) folder.

====Option 2: Fetch from CVS====

This is not signifigantly harder and means you have a more up-to-date version of the source code. Usually this means more features and different bugs, which might be more or less annoying.

1) '''Install the CVS client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/cvs

2) '''Set the CVS root'''. Run the following command, and enter the password ''anonymous'' when asked :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login
Note that simply hitting enter--not entering a password--might also work.

3) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that CVS will create a codeblocks directory for you. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however.
# cd /usr/local/src
The following command fetches the source from the CVS server :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks checkout codeblocks

===Compile the Code===

1) '''cd to codeblocks directory'''. Following our example, from CVS this would be /usr/local/src/codeblocks; from a tarball, something like /usr/local/src/codeblocks-1.0rc2 :
# cd /usr/local/src/codeblocks
or
# cd /usr/local/src/codeblocks-1.0rc2

2) '''bootstrap'''. The very first time you unpack the source (or checkout from CVS), you need to run ./bootstrap. This will create a sane building environment.
# ./bootstrap
Note: If you get weird errors here try running following command and then bootstrap again.
# find . -type f -and -not -name "*.cpp" -and -not -name "*.h" -and -not -name "*.png" -and -not -name "*.bmp" | sed "s/.*/\"\\0\"/" | xargs dos2unix

3) '''configure'''. Use 'configure --help' to see what things you can enable or disable.
# ./configure

4) '''make and make install'''.
# make
# sudo make install

===More===

to come

To run Code::Blocks:
# codeblocks

===References===

[https://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&t=29 Linux releases or compiling on Linux] from the forum

[http://sourceforge.net/cvs/?group_id=126998 Code::Blocks : CVS access instructions]

[http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services]

===Credits===

Original Author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )

Compiled packages of Code::Blocks

2006-09-12T17:27:00Z

Crzysdrs: /* SVN */

=Downloads=

==Stable Releases==
===1.0 RC2===

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec; border: solid 1px gray;"
! style="width:12em" | [[wikipedia:Operating_System|OS]]
! Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 98/NT/Me/2000/XP
| x86
| Binary Ansi
| With contrib plugins
| [http://prdownloads.sourceforge.net/codeblocks/codeblocks-1.0rc2.exe?download Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 98/NT/Me/2000/XP
| x86
| Binary Ansi
| With contrib plugins - With MinGW bundled
| [http://prdownloads.sourceforge.net/codeblocks/codeblocks-1.0rc2_mingw.exe?download Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Debian-logo_32.png]] [[wikipedia:Debian|Debian]]
| Sid
| i386
| Binary
| Probably it works on Etch i386 also
| [http://neutronic.mine.nu/unstable Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 5.10 Breezy
| x86
| Binary
| Probably it works on Dapper x86 also - Might have a problem with encoding related error messages, this is solved by editing the generated .desktop file i n /usr/share/applications/ and comment out ;encoding=UTF-8
| [http://neutronic.mine.nu/ubuntu-breezy/ Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Gentoo-logo_32.png]] [[wikipedia:Gentoo_Linux|Gentoo]]
| 2005.1
| x86/AMD64
| Ebuild
| {{dunno}}
| [http://bugs.gentoo.org/attachment.cgi?id=72819 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Gentoo-logo_32.png]] [[wikipedia:Gentoo_Linux|Gentoo]]
| 2005.1
| x86/AMD64
| Patch
| {{dunno}}
| [http://bugs.gentoo.org/attachment.cgi?id=72820 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Fedora-logo_32.png]] [[wikipedia:Fedora_Core|Redhat]]
| Fedora Core 3
| i386
| Binary
| SRPMS compatible with wxGTK-2.4 is also [http://timeoff.wsisiz.edu.pl/zrzut/codeblocks-1.0-0.2.rc2.src.rpm available].
| [http://timeoff.wsisiz.edu.pl/zrzut/codeblocks-1.0-0.2.rc2.fc3.i386.rpm Download]
| Requires wxGTK-2.4 ([http://dag.wieers.com/packages/wxGTK/ Dag repository])
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Fedora-logo_32.png]] [[wikipedia:Fedora_Core|Redhat]]
| Fedora Core 4
| i386
| Binary
| not available any more
| [http://www.neoinvent.com/cb/codeblocks-1.0-rc2.i386.rpm Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:FreeBSD-logo_32.png]] [[wikipedia:Freebsd|FreeBSD]]
| 6.0
| x86
| Binary
| {{dunno}}
| [/index.php?topic=1407.0 Download]
|
|- style="background: #ececec; border: solid 1px gray;"
! [[wikipedia:Operating_System|OS]]
! OS Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|-
|}

==Development Releases==
===SVN===

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec; border: solid 1px gray;"
! style="width:12em" | [[wikipedia:Operating_System|OS]]
! Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 2000/XP
| x86
| Binary Unicode
| With contrib plugins
| [/index.php?board=20.0 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 5.10 Breezy
| x86
| Binary
| {{dunno}}
| [/index.php?board=20.0 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 5.10 Breezy
| AMD64
| Binary
| {{dunno}}
| [http://developer.berlios.de/project/showfiles.php?group_id=5358 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:SuSE-logo-alt_32.png]] [[wikipedia:Suse|SUSE]]
| 9.3
| i686
| Binary
| {{dunno}}
| [http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Editors/codeblocks Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:SuSE-logo-alt_32.png]] [[wikipedia:Suse|SUSE]]
| 9.3
| x86 64
| Binary
| {{dunno}}
| [http://ftp.gwdg.de/pub/linux/misc/suser-drcux/93/rpm/ Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:SuSE-logo-alt_32.png]] [[wikipedia:Suse|SUSE]]
| 10.0
| i686
| Binary
| {{dunno}}
| [http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Editors/codeblocks Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:SuSE-logo-alt_32.png]] [[wikipedia:Suse|SUSE]]
| 10.0
| i586
| Binary
| rev2509 with all contrib plugins except wxsmith
| [http://www.savefile.com/files.php?fid=5856206 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:SuSE-logo-alt_32.png]] [[wikipedia:Suse|SUSE]]
| 10.0
| x86 64
| Binary
| {{dunno}}
| [http://ftp.gwdg.de/pub/linux/misc/suser-drcux/100/x86_64/ Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Slackware-logo_32.png]] [[wikipedia:Slackware|Slackware]]
| 10.2
| i686
| Binary
| {{dunno}}
| [http://www.icpnet.pl/~groman/cb-slack/ Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Slackware-logo_32.png]] [[wikipedia:Slackware|Slackware]]
| 10.2
| athlon-xp
| Binary
| {{dunno}}
| [http://www.icpnet.pl/~groman/cb-slack/ Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Mac-logo-alt.png]] [[wikipedia:Mac_os_x|Mac OS X]]
| 10.3 Panther
| PPC
| Binary
| Not ready yet
| [http://developer.berlios.de/project/showfiles.php?group_id=5358 Download]
| Bundled with wxMac 2.6 inside the app bundle
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Fedora-logo_32.png]] [[wikipedia:Fedora_Core|Redhat]]
| Fedora Core 4/5
| i686
| Binary
| With contrib plugins
| [/index.php?board=20.0 Download]
| Fedora Core 4 requires wxGTK packages e.g. from [http://ftp.freshrpms.net/pub/freshrpms/ayo/fedora/linux/4/i386/RPMS.freshrpms/ Freshrpms]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Gentoo-logo_32.png]] [[wikipedia:Gentoo|Gentoo]]
| Gentoo
| x86/AMD64
| Portage Overlay
| ?
| [http://www.stud.uni-karlsruhe.de/~uyavl/public/gentoo/codeblocks-9999-overlay-16-NO_DIGEST.tar.bz2 Download]
| [http://forums.gentoo.org/viewtopic-t-440412.html Forum Guide] [[Compiling_Code::Blocks_in_Gentoo]]
|- style="border: solid 1px gray;"
|- style="background: #ececec; border: solid 1px gray;"
! [[wikipedia:Operating_System|OS]]
! OS Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|-
|}

Installing Code::Blocks from source on Gentoo

2006-09-12T17:15:38Z

Crzysdrs: /* Code::Blocks now works fine with Unicode and wx2.6, and the build system has changed */

{{outdated}}
[[Category:Outdated]]

== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
The current suggested method for emerging Code::Blocks is through the use of custom Ebuilds. The most prominently known portage overlay for the ebuilds is located here: [http://forums.gentoo.org/viewtopic-t-440412.html Gentoo Forums Code::Blocks Portage Overlay]

=== Create your own overlay ===
Another method of pulling together your own Ebuilds and creating your own portage overlay is to view the bug report for adding Code::Blocks to portage. [http://bugs.gentoo.org/show_bug.cgi?id=89533 Gentoo Code::Blocks Package Suggestion]

== Preparing Code::Blocks from Source (Outdated) ==

'''WORK IN PROGRESS'''

( Note: This is non-official and unverified. It worked for me, but... )

===Prepare Libraries===

Code::Blocks uses the wxWidgets (http://www.wxwindows.org/) library for its GUI. wxWidgets in turn uses GTK+ (http://www.gtk.org/). GTK+ is the library which GNOME desktop uses, but GNOME is not required to use it. In fact, odds are very good that if you have a number of GUI programs installed, you already have it. wxWidgets is also very common, if slightly less so.

You need to compile the wxGTK package with the following use flag:

+gtk2

The best way of getting this done is by adding a line to /etc/portage/package.use and recompiling wxGTK :

# echo x11-libs/wxGTK gtk2 >> /etc/portage/package.use
# emerge wxGTK

Note: Code::Blocks now works fine with Unicode. So you might want to build wxGTK with +unicode flag.

===Get the source code===

For this you have 2 options:

====Option 1: Download a source tarball.====

This is easy and means you have an easily-reproduced source set.

1) '''Download a source tarball''' from [http://sourceforge.net/project/showfiles.php?group_id=126998&package_id=142469 The Download Section of CodeBlocks.org]

2) '''Extract it'''. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however. This should create a codeblocks-1.0rc2 ( or similar ) folder.

====Option 2: Fetch from CVS====

This is not signifigantly harder and means you have a more up-to-date version of the source code. Usually this means more features and different bugs, which might be more or less annoying.

1) '''Install the CVS client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/cvs

2) '''Set the CVS root'''. Run the following command, and enter the password ''anonymous'' when asked :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login
Note that simply hitting enter--not entering a password--might also work.

3) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that CVS will create a codeblocks directory for you. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however.
# cd /usr/local/src
The following command fetches the source from the CVS server :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks checkout codeblocks

===Compile the Code===

1) '''cd to codeblocks directory'''. Following our example, from CVS this would be /usr/local/src/codeblocks; from a tarball, something like /usr/local/src/codeblocks-1.0rc2 :
# cd /usr/local/src/codeblocks
or
# cd /usr/local/src/codeblocks-1.0rc2

2) '''bootstrap'''. The very first time you unpack the source (or checkout from CVS), you need to run ./bootstrap. This will create a sane building environment.
# ./bootstrap
Note: If you get weird errors here try running following command and then bootstrap again.
# find . -type f -and -not -name "*.cpp" -and -not -name "*.h" -and -not -name "*.png" -and -not -name "*.bmp" | sed "s/.*/\"\\0\"/" | xargs dos2unix

3) '''configure'''. Use 'configure --help' to see what things you can enable or disable.
# ./configure

4) '''make and make install'''.
# make
# sudo make install

===More===

to come

To run Code::Blocks:
# codeblocks

===References===

[https://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&t=29 Linux releases or compiling on Linux] from the forum

[http://sourceforge.net/cvs/?group_id=126998 Code::Blocks : CVS access instructions]

[http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services]

===Credits===

Original Author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )

Installing Code::Blocks from source on Gentoo

2006-09-12T17:14:22Z

Crzysdrs: /* The best way to compile C::B in gentoo these days is to use the codeblocks-svn ebuild which can be found in gentoo's bugzilla or in the forums */

{{outdated}}
[[Category:Outdated]]

== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
The current suggested method for emerging Code::Blocks is through the use of custom Ebuilds. The most prominently known portage overlay for the ebuilds is located here: [http://forums.gentoo.org/viewtopic-t-440412.html Gentoo Forums Code::Blocks Portage Overlay]

=== Create your own overlay ===
Another method of pulling together your own Ebuilds and creating your own portage overlay is to view the bug report for adding Code::Blocks to portage. [http://bugs.gentoo.org/show_bug.cgi?id=89533 Gentoo Code::Blocks Package Suggestion]

== Code::Blocks now works fine with Unicode and wx2.6, and the build system has changed ==

'''WORK IN PROGRESS'''

( Note: This is non-official and unverified. It worked for me, but... )

===Prepare Libraries===

Code::Blocks uses the wxWidgets (http://www.wxwindows.org/) library for its GUI. wxWidgets in turn uses GTK+ (http://www.gtk.org/). GTK+ is the library which GNOME desktop uses, but GNOME is not required to use it. In fact, odds are very good that if you have a number of GUI programs installed, you already have it. wxWidgets is also very common, if slightly less so.

You need to compile the wxGTK package with the following use flag:

+gtk2

The best way of getting this done is by adding a line to /etc/portage/package.use and recompiling wxGTK :

# echo x11-libs/wxGTK gtk2 >> /etc/portage/package.use
# emerge wxGTK

Note: Code::Blocks now works fine with Unicode. So you might want to build wxGTK with +unicode flag.

===Get the source code===

For this you have 2 options:

====Option 1: Download a source tarball.====

This is easy and means you have an easily-reproduced source set.

1) '''Download a source tarball''' from [http://sourceforge.net/project/showfiles.php?group_id=126998&package_id=142469 The Download Section of CodeBlocks.org]

2) '''Extract it'''. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however. This should create a codeblocks-1.0rc2 ( or similar ) folder.

====Option 2: Fetch from CVS====

This is not signifigantly harder and means you have a more up-to-date version of the source code. Usually this means more features and different bugs, which might be more or less annoying.

1) '''Install the CVS client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/cvs

2) '''Set the CVS root'''. Run the following command, and enter the password ''anonymous'' when asked :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login
Note that simply hitting enter--not entering a password--might also work.

3) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that CVS will create a codeblocks directory for you. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however.
# cd /usr/local/src
The following command fetches the source from the CVS server :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks checkout codeblocks

===Compile the Code===

1) '''cd to codeblocks directory'''. Following our example, from CVS this would be /usr/local/src/codeblocks; from a tarball, something like /usr/local/src/codeblocks-1.0rc2 :
# cd /usr/local/src/codeblocks
or
# cd /usr/local/src/codeblocks-1.0rc2

2) '''bootstrap'''. The very first time you unpack the source (or checkout from CVS), you need to run ./bootstrap. This will create a sane building environment.
# ./bootstrap
Note: If you get weird errors here try running following command and then bootstrap again.
# find . -type f -and -not -name "*.cpp" -and -not -name "*.h" -and -not -name "*.png" -and -not -name "*.bmp" | sed "s/.*/\"\\0\"/" | xargs dos2unix

3) '''configure'''. Use 'configure --help' to see what things you can enable or disable.
# ./configure

4) '''make and make install'''.
# make
# sudo make install

===More===

to come

To run Code::Blocks:
# codeblocks

===References===

[https://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&t=29 Linux releases or compiling on Linux] from the forum

[http://sourceforge.net/cvs/?group_id=126998 Code::Blocks : CVS access instructions]

[http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services]

===Credits===

Original Author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )