Difference between revisions of "Installing Code::Blocks"
m (add freebsd) |
m (→OpenBSD: correct defunct link) |
||
| (36 intermediate revisions by 17 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Installing Code::Blocks]] | [[Category:Installing Code::Blocks]] | ||
__TOC__ | __TOC__ | ||
| + | * [[Compiled packages of Code::Blocks]] | ||
| + | |||
== MS Windows == | == MS Windows == | ||
| Line 15: | Line 17: | ||
:* [[Installing Code::Blocks nightly build on Ubuntu]] | :* [[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]] | ||
| + | |||
| + | === 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 == | ||
| − | * [[Installing Code::Blocks from source on FreeBSD]] | + | === FreeBSD === |
| + | |||
| + | :* [[Installing Code::Blocks from source on FreeBSD]] | ||
| + | |||
| + | === OpenBSD === | ||
| + | :* https://openports.pl/path/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]] | ||
| + | |||
| + | 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:31, 5 September 2024
MS Windows
- Installing the latest official version of Code::Blocks on Windows
- Installing Code::Blocks nightly build on Windows
- Installing Code::Blocks from source on Windows
Linux
- Installing Code::Blocks from source on Linux (applies to all distros)
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
- Code::Blocks EDU-Portable - portable installation configured for learners and instructors of C/C++.
- 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!.
