Difference between revisions of "Installing Code::Blocks"

From CodeBlocks
Jump to: navigation, search
(Ubuntu Install Guide: wx-common is essential for development, not optional)
(Linux)
 
(46 intermediate revisions by 17 users not shown)
Line 1: Line 1:
[[Category:Installation\Build Instructions]]
+
[[Category:Installing Code::Blocks]]
 
__TOC__
 
__TOC__
 +
* [[Compiled packages of Code::Blocks]]
 +
 
== MS Windows ==
 
== MS Windows ==
  
The first step is to download the Code::Blocks setup file from [http://www.codeblocks.org/downloads.shtml here].
+
* [[Installing the latest official version of Code::Blocks on Windows]]
 
+
* [[Installing Code::Blocks nightly build on 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 Code::Blocks from source on Windows]]
A help text on installing a compiler will also appear. Read it!
+
  
 
== Linux ==
 
== Linux ==
=== Ubuntu Install Guide ===
 
This is a quick guide to get Code::Blocks up and running on your ubuntu based Linux distribution. It is also going to make sure you can develope wxWidgets applications on your box as well. Look at the bottom of this guide for a complete command line that will install all the packages in one operation.
 
  
1. Get the latest daily build of Code::Blocks from the [http://forums.codeblocks.org/index.php?board=20.0 forum].
+
* [[Installing Code::Blocks from source on Linux]] (applies to all distros)
  
2. Install Code::Blocks.
+
=== Ubuntu ===
sudo dpkg -i <Name_Of_Daily_Build.deb>
+
  
3. Install the compiler.
+
:* [[Installing Code::Blocks nightly build on Ubuntu]]
sudo apt-get install build-essential
+
  
4. Install the debugger.
+
=== Debian ===
sudo apt-get install gdb
+
  
5. Install wxWidgets library. (This package is all that is needed to run any application that uses wxWidgets. ie. Code::Blocks)
+
:* [http://apt.jenslody.de/ Installing Code::Blocks nightly build on Debian]
sudo apt-get install libwxgtk2.6-0
+
  
6. Install the wxWidgets developement packages. (This is used to develop wxWidgets applications of your own.)
+
=== Fedora ===
sudo apt-get install libwxgtk2.6-dev wx2.6-headers wx-common
+
  
7. ''(OPTIONAL)'' Install the wxWidgets documentation.
+
:* [[Installing Code::Blocks nightly build on Fedora]]
sudo apt-get install wx2.6-doc
+
  
 +
=== Blag ===
  
----
+
:* [[Installing Code::Blocks nightly build on Blag]]
  
NOTE: Here is a complete command line for steps 3 - 7. Watch for word wrap.
+
=== Gentoo ===
sudo apt-get install build-essential gdb libwxgtk2.6-0 libwxgtk2.6-dev wx2.6-headers wx2.6-doc wx-common
+
  
Without optional steps:
+
:* [[Installing Code::Blocks from source on Gentoo]]
sudo apt-get install build-essential gdb libwxgtk2.6-0 libwxgtk2.6-dev wx2.6-headers wx-common
+
 
 +
=== Platypux ===
 +
 
 +
:* [[Installing Code::Blocks with LZM binary on Platypux]]
 +
 
 +
=== Arch Linux ===
 +
 
 +
:* [[Installing Code::Blocks from source on Arch Linux]]
 +
 
 +
=== Mageia 7 ===
 +
 
 +
:* [[Installing Code::Blocks from source on Mageia 7]]
 +
 
 +
=== 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 ==
 
== 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 17:44, 4 January 2021

MS Windows

Linux

Ubuntu

Debian

Fedora

Blag

Gentoo

Platypux

Arch Linux

Mageia 7

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!