Installing Code::Blocks - Revision history

Jggimi: /* OpenBSD */ correct defunct link

2024-09-05T14:31:05Z

OpenBSD: correct defunct link

Mgimenez: /* Mac OS X */ Added information about Macports working with all versions

2023-11-13T14:35:39Z

Mac OS X: Added information about Macports working with all versions

Mgimenez: /* Working on Code::Blocks sources from within Code::Blocks! */ Specify new folder names and usage of the update script

2022-01-22T11:58:36Z

Working on Code::Blocks sources from within Code::Blocks!: Specify new folder names and usage of the update script

Gandi: /* Linux */

2021-01-04T16:44:14Z

Linux

Bluehazzard: Add link to installing Arch on Linux

2019-08-08T21:25:19Z

Add link to installing Arch on Linux

Alpha: Added derivatives.

2012-03-08T05:06:00Z

Added derivatives.

Alpha: Moved TOC.

2011-10-15T13:47:31Z

Moved TOC.

Freem: typo on src (was scr)

2011-08-02T19:09:20Z

typo on src (was scr)

Stahta01: /* FreeBSD */

2010-09-29T19:02:07Z

FreeBSD

Platypux at 09:01, 12 July 2010

2010-07-12T09:01:06Z

@@ Line 59: / Line 59: @@
 === OpenBSD ===
-:* http://openports.se/devel/codeblocks
+:* https://openports.pl/path/devel/codeblocks
 == Solaris ==

← Older revision		Revision as of 14:35, 13 November 2023
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 ==

@@ Line 83: / Line 83: @@
 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".
+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 "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!

@@ Line 40: / Line 40: @@
 :* [[Installing Code::Blocks from source on Arch Linux]]
 === RPM based distributions ===
@@ Line 47: / Line 51: @@
 :* [[Installing Code::Blocks nightly build on RPM based distributions]]
 :* [[Installing Code::Blocks from source on RPM based distributions]]
 == BSD ==

@@ Line 36: / Line 36: @@
 :* [[Installing Code::Blocks with LZM binary on Platypux]]
 === RPM based distributions ===
@@ Line 43: / Line 47: @@
 :* [[Installing Code::Blocks nightly build on RPM based distributions]]
 :* [[Installing Code::Blocks from source on RPM based distributions]]
 == BSD ==

@@ Line 64: / Line 64: @@
 * [[Installing Code::Blocks from source on Mac OS X]]
 ==Working on Code::Blocks sources from within Code::Blocks!==
@@ Line 71: / Line 77: @@
 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!
+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!

@@ Line 1: / Line 1: @@
 [[Category:Installing Code::Blocks]]
+__TOC__
-[[Compiled packages of Code::Blocks]]
+* [[Compiled packages of Code::Blocks]]
 == MS Windows ==

← Older revision		Revision as of 19:02, 29 September 2010
Line 49:		Line 49:

	:* [[Installing Code::Blocks from source on FreeBSD]]		:* [[Installing Code::Blocks from source on FreeBSD]]
		+
		+	=== OpenBSD ===
		+	:* http://openports.se/devel/codeblocks

	== Solaris ==		== Solaris ==

← Older revision		Revision as of 09:01, 12 July 2010
Line 32:		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 ===