Difference between revisions of "Installing Code::Blocks"

From Code::Blocks
m (link "new" articles)
(→‎Mac OS X: Added information about Macports working with all versions)
 
(39 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 ==
  
Line 8: Line 10:
  
 
== Linux ==
 
== Linux ==
 +
 +
* [[Installing Code::Blocks from source on Linux]] (applies to all distros)
  
 
=== Ubuntu ===
 
=== Ubuntu ===
−
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 develop 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 [/index.php?board=20.0 forum].
+
:* [[Installing Code::Blocks nightly build on Ubuntu]]
 +
 
 +
=== Debian ===
 +
 
 +
:* [http://apt.jenslody.de/ Installing Code::Blocks nightly build on Debian]
 +
 
 +
=== Fedora ===
 +
 
 +
:* [[Installing Code::Blocks nightly build on Fedora]]
 +
 
 +
=== Blag ===
 +
 
 +
:* [[Installing Code::Blocks nightly build on Blag]]
 +
 
 +
=== Gentoo ===
 +
 
 +
:* [[Installing Code::Blocks from source on Gentoo]]
 +
 
 +
=== Platypux ===
 +
 
 +
:* [[Installing Code::Blocks with LZM binary on Platypux]]
  
−
2. Install Code::Blocks.
+
=== Arch Linux ===
−
sudo dpkg -i <Name_Of_Daily_Build.deb>
 
  
−
3. Install the compiler.
+
:* [[Installing Code::Blocks from source on Arch Linux]]
−
sudo apt-get install build-essential
 
  
−
4. Install the debugger.
+
=== Mageia 7 ===
−
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)
+
:* [[Installing Code::Blocks from source on Mageia 7]]
−
sudo apt-get install libwxgtk2.6-0
 
  
−
6. Install the wxWidgets developement packages. (This is used to develop wxWidgets applications of your own.)
+
=== RPM based distributions ===
−
sudo apt-get install libwxgtk2.6-dev wx2.6-headers wx-common
 
  
−
7. ''(OPTIONAL)'' Install the wxWidgets documentation.
+
Such as: Red Hat Linux, Yellow Dog Linux, Fedora Core, CentOS, etc. etc.
−
sudo apt-get install wx2.6-doc
 
  
 +
:* [[Installing Code::Blocks nightly build on RPM based distributions]]
 +
:* [[Installing Code::Blocks from source on RPM based distributions]]
  
−
----
+
== BSD ==
  
 +
=== FreeBSD ===
  
−
NOTE: Here is a complete command line for steps 3 - 7. Watch for word wrap.
+
:* [[Installing Code::Blocks from source on FreeBSD]]
  
−
sudo apt-get install build-essential gdb libwxgtk2.6-0 libwxgtk2.6-dev wx2.6-headers wx2.6-doc wx-common
+
=== OpenBSD ===
 +
:* http://openports.se/devel/codeblocks
  
 +
== Solaris ==
  
−
Without optional steps:
+
* [[Installing Code::Blocks from source on Solaris]]
−
sudo apt-get install build-essential gdb libwxgtk2.6-0 libwxgtk2.6-dev wx2.6-headers wx-common
 
  
 
== 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]]
 +
 +
You can use also use [https://www.macports.org/ Macports] to install Code::Blocks on MacOS X upto Sonoma.
 +
 +
== 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 .../trunk/src , one named "devel30" and another one named "output30" (the number depends on wxWidgets version).
 +
 +
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 "output30/CodeBlocks.exe" executable. Code::Blocks' project settings are such that all output goes under "devel30", so you can edit Code::Blocks' sources inside Code::Blocks and, when pressing "Run", it will run the "devel30/CodeBlocks.exe" executable ;). This way, you can't ruin the main executable you're using (under "output30"). When your changes satisfy you and all works well, quit Code::Blocks, open a console, change to the src directory and run "update30.bat" (Windows) or "./update30" (Linux) from command line. Then re-launch "output30/CodeBlocks.exe". You'll be working on your brand new IDE!.

Latest revision as of 14:35, 13 November 2023

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

You can use also use Macports to install Code::Blocks on MacOS X upto Sonoma.

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 .../trunk/src , one named "devel30" and another one named "output30" (the number depends on wxWidgets version).

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 "output30/CodeBlocks.exe" executable. Code::Blocks' project settings are such that all output goes under "devel30", so you can edit Code::Blocks' sources inside Code::Blocks and, when pressing "Run", it will run the "devel30/CodeBlocks.exe" executable ;). This way, you can't ruin the main executable you're using (under "output30"). When your changes satisfy you and all works well, quit Code::Blocks, open a console, change to the src directory and run "update30.bat" (Windows) or "./update30" (Linux) from command line. Then re-launch "output30/CodeBlocks.exe". You'll be working on your brand new IDE!.

Retrieved from "https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks&oldid=9768"