Code::Blocks - User contributions [en]

Installing Code::Blocks from source on Gentoo

2010-07-04T23:26:30Z

Keenblade: /* Create your own overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
Code::Blocks is available in Portage. So the current suggested method for installing Code::Blocks on Gentoo is as simple as:

# emerge -av codeblocks

However you may want to use development version of Code::Blocks which is in portage, too. Previously it was available through the use of custom ebuild that is located here: [http://forums.gentoo.org/viewtopic-t-588089.html Gentoo Forums Code::Blocks Portage Overlay] But since it is in portage, there is no need for it. To install the development version (codeblocks-9999.ebuild), all you have to do is just adding the line (without quotes) "dev-util/codeblocks **" into your /etc/portage/package.keywords file. And then install as usual:

# emerge -av codeblocks

=== 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]
To create an overlay, please read [http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]. But since Code::Blocks is already in portage you should not need this. Just use the current suggested method as stated above.

== 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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )

Installing Code::Blocks from source on Gentoo

2010-07-04T23:25:06Z

Keenblade: /* Create your own overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
Code::Blocks is available in Portage. So the current suggested method for installing Code::Blocks on Gentoo is as simple as:

# emerge -av codeblocks

However you may want to use development version of Code::Blocks which is in portage, too. Previously it was available through the use of custom ebuild that is located here: [http://forums.gentoo.org/viewtopic-t-588089.html Gentoo Forums Code::Blocks Portage Overlay] But since it is in portage, there is no need for it. To install the development version (codeblocks-9999.ebuild), all you have to do is just adding the line (without quotes) "dev-util/codeblocks **" into your /etc/portage/package.keywords file. And then install as usual:

# emerge -av codeblocks

=== 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]
To create an overlay, please read [http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]. But since Code::Blocks is already in portage you should not need this. Just use the recommended way as stated above.

== 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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )

Installing Code::Blocks from source on Gentoo

2010-07-04T23:23:43Z

Keenblade: /* Create your own overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
Code::Blocks is available in Portage. So the current suggested method for installing Code::Blocks on Gentoo is as simple as:

# emerge -av codeblocks

However you may want to use development version of Code::Blocks which is in portage, too. Previously it was available through the use of custom ebuild that is located here: [http://forums.gentoo.org/viewtopic-t-588089.html Gentoo Forums Code::Blocks Portage Overlay] But since it is in portage, there is no need for it. To install the development version (codeblocks-9999.ebuild), all you have to do is just adding the line (without quotes) "dev-util/codeblocks **" into your /etc/portage/package.keywords file. And then install as usual:

# emerge -av codeblocks

=== 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]
To create an overlay, please read [http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]. But since codeblocks is in portage you should not need this. Just use the recommended way as stated above.

== 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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )

Installing Code::Blocks from source on Gentoo

2010-07-04T23:12:05Z

Keenblade: /* Subversion Portage Overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
Code::Blocks is available in Portage. So the current suggested method for installing Code::Blocks on Gentoo is as simple as:

# emerge -av codeblocks

However you may want to use development version of Code::Blocks which is in portage, too. Previously it was available through the use of custom ebuild that is located here: [http://forums.gentoo.org/viewtopic-t-588089.html Gentoo Forums Code::Blocks Portage Overlay] But since it is in portage, there is no need for it. To install the development version (codeblocks-9999.ebuild), all you have to do is just adding the line (without quotes) "dev-util/codeblocks **" into your /etc/portage/package.keywords file. And then install as usual:

# emerge -av codeblocks

=== 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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )

Installing Code::Blocks from source on Gentoo

2010-07-04T23:06:40Z

Keenblade: /* Subversion Portage Overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
Code::Blocks is available in Portage. So the current suggested method for installing Code::Blocks on Gentoo is as simple as:

# emerge -av codeblocks

However you may want to use development version of Code::Blocks which is in portage, too. Previously it was available through the use of custom ebuild that is located here: [http://forums.gentoo.org/viewtopic-t-588089.html Gentoo Forums Code::Blocks Portage Overlay] But since it is in portage, there is no need for it. To install the development version (codeblocks-9999.ebuild), all you have to do is just adding the line "dev-util/codeblocks **" into your /etc/portage/package.keywords file. And then install as usual:

# emerge -av codeblocks

=== 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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )

Installing Code::Blocks from source on Gentoo

2010-07-04T23:04:56Z

Keenblade: /* Subversion Portage Overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
Code::Blocks is available in Portage. So the current suggested method for installing Code::Blocks on Gentoo is as simple as:

# emerge -av codeblocks

However you may want to use development version of Code::Blocks which is in portage, too. Previously it was available through the use of custom ebuild that is located here: [http://forums.gentoo.org/viewtopic-t-588089.html Gentoo Forums Code::Blocks Portage Overlay] But since it is in portage, there is no need for it. To install the development version (codeblocks-9999.ebuild), all you have to do is just by adding "dev-util/codeblocks **" into your /etc/portage/package.keywords file. And then install as usual:

# emerge -av codeblocks

=== 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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )

Compiled packages of Code::Blocks

2008-09-13T10:41:58Z

Keenblade: /* SVN */

== Stable Releases ==

=== 8.02 ===

{| 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/Vista
| x86
| Binary
| With contrib plugins
| [http://downloads.sourceforge.net/codeblocks/codeblocks-8.02-setup.exe Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 2000/XP/Vista
| x86
| Binary Ansi
| With contrib plugins - With MinGW bundled
| [http://downloads.sourceforge.net/codeblocks/codeblocks-8.02mingw-setup.exe Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Debian-logo_32.png]] [[wikipedia:Debian|Debian]]
|
| i386
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks-8.02debian-i386.tar.gz Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Debian-logo_32.png]] [[wikipedia:Debian|Debian]]
|
| AMD64
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks-8.02debian-amd64.tar.gz Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 7.10 Gutsy
| x86
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks_8.02-0ubuntu1.deb.tar.gz Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 7.10 Gutsy
| AMD64
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks-8.02-amd64.tar.gz Download]
|
|- style="background: #ececec; border: solid 1px gray;"
! [[wikipedia:Operating_System|OS]]
! OS Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|-
|}

=== 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
| No longer supported by the previous package author.
|
|
|- 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
| No longer supported by the previous package author.
|
|
|- 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|Fedora]]
| 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|Fedora]]
| 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.1
| 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]]
| 98/NT/Me/2000/XP
| x86
| Binary
| 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_Linux|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_Linux|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_Linux|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_Linux|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_Linux|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
| ?
| [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:Mac-logo-alt.png]] [[wikipedia:Mac_OS_X|Mac OS X]]
| 10.4 Tiger
| PPC/X86
| Binary
| ?
| [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="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Mac-logo-alt.png]] [http://www.macports.org/ MacPorts]
| Darwin
| PPC/X86
| Source
| ?
|
| [[Installing Code::Blocks from source on Mac OS X]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Fedora-logo_32.png]] [[wikipedia:Fedora_Core|Fedora]]
| 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:CentOS-logo_32.png]] [[wikipedia:CentOS|CentOS]]
| CentOS 3/4
| i686
| Source
| ?
|
| [[Installing_Code::Blocks_from_source_on_RPM_based_distributions]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Gentoo-logo_32.png]] [[wikipedia:Gentoo_Linux|Gentoo]]
| Gentoo
| x86/AMD64
| Portage Overlay
| With contrib plugins by "contrib" useflag
| [http://www.savefile.com/projects/808517256 Download]
| [http://forums.gentoo.org/viewtopic-t-588089-highlight-codeblocks+svn.html Forum Guide New]
: [http://forums.gentoo.org/viewtopic-t-440412.html Forum Guide by retired Gentoo developer] [[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

2008-09-13T10:29:26Z

Keenblade: /* Subversion Portage Overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== Current Code::Blocks Compilation Methods for Gentoo ==

=== Subversion Portage Overlay ===
Code::Blocks is available in Portage. So the current suggested method for installing Code::Blocks on Gentoo is as simple as:

# emerge -av codeblocks

However you may want to use development version of Code::Blocks which is available through the use of custom Ebuilds. The most prominently known portage overlay for the the ebuilds is located here: [http://forums.gentoo.org/viewtopic-t-588089.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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )

Installing Code::Blocks from source on Gentoo

2008-09-13T09:48:51Z

Keenblade: /* Subversion Portage Overlay */

[[Category: Installing Code::Blocks]]
[[Category: Installing Code::Blocks from source]]
== 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-588089.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 SVN====

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 SVN client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/subversion

2) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that SVN 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 SVN server :
# svn checkout svn://svn.berlios.de/codeblocks/trunk

===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

[https://www.codeblocks.org/source_code.shtml Code::Blocks : SVN access instructions]

===Credits===

First version author: me22 ( me22.ca@gmail.com )
Some changes: sleipner ( themacgyver@gmail.com )
More updating: Crzysdrs
And more updating: d1mk4 ( d1mk4nah@gmail.com )