Code::Blocks - User contributions [en]

CodeBlocks:Community Portal

2005-03-15T23:24:33Z

70.80.121.34:

[https://www.codeblocks.org/ Code::Blocks Main Site]

[https://www.codeblocks.org/modules.php?op=modload&name=PNphpBB2&file=index Code::Blocks Forum]

[http://sourceforge.net/projects/codeblocks/ Code::Blocks SourceForge.net Project Page]

[http://codeblocks.tigris.org/ Code::Blocks Tigris Project Page]

Installing Code::Blocks from source on Gentoo

2005-03-15T23:17:31Z

70.80.121.34: /* More */

'''WORK IN PROGRESS'''

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

===Prepare Libraries===

Code::Blocks uses the [http://www.wxwindows.org/ wxWidgets] library for its GUI. wxWidgets is turn uses [http://www.gtk.org/ GTK+]. GTK+ is the library the 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. The trick with wxWidgets and Code::Blocks is that Code::Blocks can only use the gtk2, non-unicode version of wxWidgets

This means that you need to compile the wxGTK package with the following use flags settings:
+no_wxgtk1 +gtk2 -unicode
The best way of getting these set is by adding a line to /etc/portage/package.use and recompiling wxGTK :
# echo x11-libs/wxGTK no_wxgtk1 gtk2 -unicode >> /etc/portage/package.use
# emerge wxGTK

===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 [https://www.codeblocks.org/modules.php?op=modload&name=Downloads&file=index&req=viewsdownload&sid=3 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.0-beta5 ( 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

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 the directory with the Makefile'''. Following our example, from CVS this would be /usr/local/src/codeblocks/src; from a tarball, something like /usr/local/src/CodeBlocks-1.0-beta5 :
# cd /usr/local/src/codeblocks/src
or
# cd /usr/local/src/CodeBlocks-1.0-beta5
If neither of those works, you can always use find to look for it :
# find <parent directory you extracted to> -name Makefile.unix

2) '''Build the sources'''. There's no configuration nessesary, just let make go to work :
# make -f Makefile.unix
# make -f Makefile.unix update
The first line does the actual compiling. The second moves the nessesary things to the output directory, zips some resources, and performs other miscellaneous nessesary tasks.

===More===

to come

For now ( assuming bash shell ):
$ cd /usr/local/src/codeblocks/src/output
$ LD_LIBRARY_PATH="." ./codeblocks.exe

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

Installing Code::Blocks from source on Gentoo

2005-03-15T23:15:06Z

70.80.121.34: /* Compile the Code */

'''WORK IN PROGRESS'''

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

===Prepare Libraries===

Code::Blocks uses the [http://www.wxwindows.org/ wxWidgets] library for its GUI. wxWidgets is turn uses [http://www.gtk.org/ GTK+]. GTK+ is the library the 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. The trick with wxWidgets and Code::Blocks is that Code::Blocks can only use the gtk2, non-unicode version of wxWidgets

This means that you need to compile the wxGTK package with the following use flags settings:
+no_wxgtk1 +gtk2 -unicode
The best way of getting these set is by adding a line to /etc/portage/package.use and recompiling wxGTK :
# echo x11-libs/wxGTK no_wxgtk1 gtk2 -unicode >> /etc/portage/package.use
# emerge wxGTK

===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 [https://www.codeblocks.org/modules.php?op=modload&name=Downloads&file=index&req=viewsdownload&sid=3 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.0-beta5 ( 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

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 the directory with the Makefile'''. Following our example, from CVS this would be /usr/local/src/codeblocks/src; from a tarball, something like /usr/local/src/CodeBlocks-1.0-beta5 :
# cd /usr/local/src/codeblocks/src
or
# cd /usr/local/src/CodeBlocks-1.0-beta5
If neither of those works, you can always use find to look for it :
# find <parent directory you extracted to> -name Makefile.unix

2) '''Build the sources'''. There's no configuration nessesary, just let make go to work :
# make -f Makefile.unix
# make -f Makefile.unix update
The first line does the actual compiling. The second moves the nessesary things to the output directory, zips some resources, and performs other miscellaneous nessesary tasks.

===More===

to come

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

Installing Code::Blocks from source on Gentoo

2005-03-15T22:46:37Z

70.80.121.34: /* Credits */

'''WORK IN PROGRESS'''

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

===Prepare Libraries===

Code::Blocks uses the [http://www.wxwindows.org/ wxWidgets] library for its GUI. wxWidgets is turn uses [http://www.gtk.org/ GTK+]. GTK+ is the library the 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. The trick with wxWidgets and Code::Blocks is that Code::Blocks can only use the gtk2, non-unicode version of wxWidgets

This means that you need to compile the wxGTK package with the following use flags settings:
+no_wxgtk1 +gtk2 -unicode
The best way of getting these set is by adding a line to /etc/portage/package.use and recompiling wxGTK :
# echo x11-libs/wxGTK no_wxgtk1 gtk2 -unicode >> /etc/portage/package.use
# emerge wxGTK

===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 [https://www.codeblocks.org/modules.php?op=modload&name=Downloads&file=index&req=viewsdownload&sid=3 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.0-beta5 ( 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

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 the directory with the Makefile'''. From CVS this will be <?>; from a tarball, <?> :
# cd <?>
or
# cd <?>

2) '''Build the sources'''. There's no configuration nessesary, just let make go to work :
# make -f Makefile.unix
# make -f Makefile.unix update

===More===

to come

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

Installing Code::Blocks from source on Gentoo

2005-03-15T22:45:15Z

70.80.121.34: /* Compile the Code */

'''WORK IN PROGRESS'''

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

===Prepare Libraries===

Code::Blocks uses the [http://www.wxwindows.org/ wxWidgets] library for its GUI. wxWidgets is turn uses [http://www.gtk.org/ GTK+]. GTK+ is the library the 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. The trick with wxWidgets and Code::Blocks is that Code::Blocks can only use the gtk2, non-unicode version of wxWidgets

This means that you need to compile the wxGTK package with the following use flags settings:
+no_wxgtk1 +gtk2 -unicode
The best way of getting these set is by adding a line to /etc/portage/package.use and recompiling wxGTK :
# echo x11-libs/wxGTK no_wxgtk1 gtk2 -unicode >> /etc/portage/package.use
# emerge wxGTK

===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 [https://www.codeblocks.org/modules.php?op=modload&name=Downloads&file=index&req=viewsdownload&sid=3 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.0-beta5 ( 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

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 the directory with the Makefile'''. From CVS this will be <?>; from a tarball, <?> :
# cd <?>
or
# cd <?>

2) '''Build the sources'''. There's no configuration nessesary, just let make go to work :
# make -f Makefile.unix
# make -f Makefile.unix update

===More===

to come

===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 ) For some reason this Wiki is spazzing when I try and use a non-anonymous account.