Difference between revisions of "Installing Code::Blocks"

From Code::Blocks
m (→‎Working on Code::Blocks sources from within Code::Blocks!: Specify new folder names and usage of the update script)
m (→‎OpenBSD: correct defunct link)
 
(One intermediate revision by one other user not shown)
Line 59: Line 59:
  
 
=== OpenBSD ===
 
=== OpenBSD ===
:* http://openports.se/devel/codeblocks
+
:* https://openports.pl/path/devel/codeblocks
  
 
== Solaris ==
 
== Solaris ==
Line 72: Line 72:
  
 
* [[Installing Code::Blocks from source 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 ==
 
== Derivatives ==

Latest revision as of 14:31, 5 September 2024

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!.