Difference between revisions of "Installing Code::Blocks"

From CodeBlocks
Jump to: navigation, search
(Add link to installing Arch on Linux)
 
(50 intermediate revisions by 18 users not shown)
Line 1: Line 1:
[[Category:Installation]]
+
[[Category:Installing Code::Blocks]]
== Code::Blocks installation procedure under Windows ==
+
__TOC__
 +
* [[Compiled packages of Code::Blocks]]
  
The first step is to download the Code::Blocks setup file from [http://sourceforge.net/project/showfiles.php?group_id=126998 here].
+
== MS Windows ==
  
After you download the setup file you selected, launch it to start the setup process. The setup program is a standard installer for Windows. Just press "Next" after reading each screen. You will be given the chance to read the program license, enter the installation directory and select which plugins you want installed.
+
* [[Installing the latest official version of Code::Blocks on Windows]]
A help text on installing a compiler will also appear. Read it!
+
* [[Installing Code::Blocks nightly build on Windows]]
 +
* [[Installing Code::Blocks from source on Windows]]
  
'''''Note:'''''
+
== Linux ==
''Most other IDEs, behave strangely when installed in a directory whose path contains spaces. Code::Blocks IDE '''does not''' suffer from this problem! Feel free to install it in whichever path you like!''
+
  
'''''Note 2:'''''
+
* [[Installing Code::Blocks from source on Linux]] (applies to all distros)
''If you 'll be using MinGW GCC with Code::Blocks, two MinGW programs <u>do have problems</u> with spaces in filenames: <code>windres.exe</code> (resource compiler) and <code>gdb.exe</code> (GNU debugger). If you plan on using any of these two programs, avoid placing your projects in paths containing spaces.''
+
  
== Code::Blocks installation procedure under Linux ==
+
=== Ubuntu ===
  
'''This article is not uptodate'''
+
:* [[Installing Code::Blocks nightly build on Ubuntu]]
please have a look at this [http://wiki.codeblocks.org/index.php?title=Compiling_Code::Blocks_in_Linux_%28applies_to_all_distros%29 tutorial]
+
  
Due to the large amount of possible combinations on the Linux platform, Code::Blocks isn't provided in already compiled form. Until now, you'll have to do with the source distribution. Since september 2005, compiling under Linux has become much more standardised and easy, due to the use of the Autotools package.
+
=== Debian ===
  
=== Novell SuSE Linux 9.3 ===
+
:* [http://apt.jenslody.de/ Installing Code::Blocks nightly build on Debian]
SuSE Linux 9.3 is shipped with wxWidgets 2.5.3, but the latest CVS does compile with the shipped wxWidgets. All you have to do is:
+
 
1. Change to the directory where you want the codeblocks source
+
=== Fedora ===
2. execute the following command:
+
 
  cvs -z5 -d:pserver:[email protected]:/cvsroot/codeblocks co -P codeblocks
+
:* [[Installing Code::Blocks nightly build on Fedora]]
3. change to the directory where you put the codeblocks source<br/>
+
 
4. execute
+
=== Blag ===
  ./bootstrap
+
 
that should make the different needed files for your system.<br/>
+
:* [[Installing Code::Blocks nightly build on Blag]]
5. execute
+
 
  ./configure
+
=== Gentoo ===
6. execute
+
 
  make
+
:* [[Installing Code::Blocks from source on Gentoo]]
7. change the user to root ('su')<br/>
+
 
8. execute
+
=== Platypux ===
  make install
+
 
That should take care of the installation procedure.
+
:* [[Installing Code::Blocks with LZM binary on Platypux]]
 +
 
 +
=== Arch Linux ===
 +
 
 +
:* [[Installing Code::Blocks from source on Arch Linux]]
 +
 
 +
=== RPM based distributions ===
 +
 
 +
Such as: Red Hat Linux, Yellow Dog Linux, Fedora Core, CentOS, etc. etc.
 +
 
 +
:* [[Installing Code::Blocks nightly build on RPM based distributions]]
 +
:* [[Installing Code::Blocks from source on RPM based distributions]]
 +
 
 +
 
 +
== BSD ==
 +
 
 +
=== FreeBSD ===
 +
 
 +
:* [[Installing Code::Blocks from source on FreeBSD]]
 +
 
 +
=== OpenBSD ===
 +
:* http://openports.se/devel/codeblocks
 +
 
 +
== Solaris ==
 +
 
 +
* [[Installing Code::Blocks from source on Solaris]]
 +
 
 +
== 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 from source on Mac OS X]]
 +
 
 +
== 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.
 +
 
 +
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!

Latest revision as of 23:25, 8 August 2019

MS Windows

Linux

Ubuntu

Debian

Fedora

Blag

Gentoo

Platypux

Arch Linux

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!