Difference between revisions of "Installing Code::Blocks"

From Code::Blocks
m
(Added derivatives.)
(9 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
[[Category:Installing Code::Blocks]]
 
[[Category:Installing Code::Blocks]]
 
+
__TOC__
[[Compiled packages of Code::Blocks]]
+
* [[Compiled packages of Code::Blocks]]
  
 
== MS Windows ==
 
== MS Windows ==
Line 12: Line 12:
  
 
* [[Installing Code::Blocks from source on Linux]] (applies to all distros)
 
* [[Installing Code::Blocks from source on Linux]] (applies to all distros)
* [[Installing Code::Blocks before SVN 3893 from source on Linux]] (applies to all distros)
 
  
 
=== Ubuntu ===
 
=== Ubuntu ===
Line 20: Line 19:
 
=== Debian ===
 
=== Debian ===
  
:* [http://jens.lody.name/debian/ Installing Code::Blocks nightly build on Debian]
+
:* [http://apt.jenslody.de/ Installing Code::Blocks nightly build on Debian]
  
 
=== Fedora ===
 
=== Fedora ===
Line 33: Line 32:
  
 
:* [[Installing Code::Blocks from source on Gentoo]]
 
:* [[Installing Code::Blocks from source on Gentoo]]
 +
 +
=== Platypux ===
 +
 +
:* [[Installing Code::Blocks with LZM binary on Platypux]]
  
 
=== RPM based distributions ===
 
=== RPM based distributions ===
Line 46: Line 49:
  
 
:* [[Installing Code::Blocks from source on FreeBSD]]
 
:* [[Installing Code::Blocks from source on FreeBSD]]
 +
 +
=== OpenBSD ===
 +
:* http://openports.se/devel/codeblocks
  
 
== Solaris ==
 
== Solaris ==
Line 52: Line 58:
  
 
== Mac OS X ==
 
== Mac OS X ==
 +
 +
* [[Installing the latest official version of Code::Blocks on Mac OS X]]
  
 
* [[Installing Code::Blocks nightly build on Mac OS X]]
 
* [[Installing Code::Blocks nightly build on Mac OS X]]
Line 57: Line 65:
 
* [[Installing Code::Blocks from source on Mac OS X]]
 
* [[Installing Code::Blocks from source on Mac OS X]]
  
===Working on Code::Blocks sources from within Code::Blocks!===
+
== Derivatives ==
 +
 
 +
* [http://codeblocks.codecutter.org/ Code::Blocks EDU-Portable] - portable installation configured for learners and instructors of C/C++.
 +
 
 +
* [http://darmar.vgtu.lt/ Code::Blocks IDE for Fortran] - additional features for Fortran oriented programmers.
 +
 
 +
==Working on Code::Blocks sources from within Code::Blocks!==
  
---------------------------------------------------------
+
The following applies for all platforms where you have Code::Blocks installed and working.
The following apply for all platforms where you have Code::Blocks installed and working.
 
  
After correct install of Code::Blocks you will find two folders under .../trunc/scr , a directory named "devel" and another one named "output".
+
After correct install of Code::Blocks you will find two folders under .../trunc/src , a directory named "devel" and another one named "output".
 
These two folders will contain the same files and directory structure and you can use the IDE from either of these two directories. This structure has been created so that you can work in Code::Blocks while editing Code::Blocks' sources ;).
 
These two folders will contain the same files and directory structure and you can use the IDE from either of these two directories. This structure has been created so that you can work in Code::Blocks while editing Code::Blocks' sources ;).
Basically, you 'll be using the "output/CodeBlocks.exe" executable. Code::Blocks' project settings are such that all output goes under "devel". So you can edit Code::Blocks' sources inside Code::Blocks and, when pressing "Run", it will run the "devel/CodeBlocks.exe" executable ;). This way, you can't ruin the main executable you 're using (under "output"). When your changes satisfy you and all works well, quit Code::Blocks, run "make update" from command line and re-launch "output/CodeBlocks.exe". You 'll be working on your brand new IDE!
+
Basically, you'll be using the "output/CodeBlocks.exe" executable. Code::Blocks' project settings are such that all output goes under "devel". So you can edit Code::Blocks' sources inside Code::Blocks and, when pressing "Run", it will run the "devel/CodeBlocks.exe" executable ;). This way, you can't ruin the main executable you're using (under "output"). When your changes satisfy you and all works well, quit Code::Blocks, run "make update" from command line and re-launch "output/CodeBlocks.exe". You'll be working on your brand new IDE!

Revision as of 05:06, 8 March 2012

MS Windows

Linux

Ubuntu

Debian

Fedora

Blag

Gentoo

Platypux

RPM based distributions

Such as: Red Hat Linux, Yellow Dog Linux, Fedora Core, CentOS, etc. etc.

BSD

FreeBSD

OpenBSD

Solaris

Mac OS X

Derivatives

Working on Code::Blocks sources from within Code::Blocks!

The following applies for all platforms where you have Code::Blocks installed and working.

After correct install of Code::Blocks you will find two folders under .../trunc/src , a directory named "devel" and another one named "output". These two folders will contain the same files and directory structure and you can use the IDE from either of these two directories. This structure has been created so that you can work in Code::Blocks while editing Code::Blocks' sources ;). Basically, you'll be using the "output/CodeBlocks.exe" executable. Code::Blocks' project settings are such that all output goes under "devel". So you can edit Code::Blocks' sources inside Code::Blocks and, when pressing "Run", it will run the "devel/CodeBlocks.exe" executable ;). This way, you can't ruin the main executable you're using (under "output"). When your changes satisfy you and all works well, quit Code::Blocks, run "make update" from command line and re-launch "output/CodeBlocks.exe". You'll be working on your brand new IDE!