Monthly Archives: April 2009

GCC-4.4.0-MinGW Binary

Posted on by
Reply

Edited (12-February-2012):
The download links do not work anymore. I also do not have a copy of those files. If you need a recent GCC build head over to mingw.org website.

GCC-4.4.0 has been released recently. I have managed to compile it as a MinGW build and I want to share that with others. The package can be downloaded from the following links. Please download both the files and extract them to C:\MinGW folder. Then extract Win32API, MinGW Runtime, pthreads-win (If you want to use OpenMP) package to the same folder. Now you’ll be able to use gcc-4.4 on Windows.

Download Links: Continue reading →

Creating Portable Code::Blocks: Part 2

Posted on by
15

To update all I have committed patch in trunk (in revision 5334). It should be available with the next nightly.

To run Code::Blocks portably you can write a batch file, set APPDATA variable to any directory you want and then launch Code::Blocks.

Alternatively you can download the CbLauncher v0.1.1 from my blog to run Code::Blocks portably.

Steps to use Cblauncher: Continue reading →

Creating Portable Version of Code::Blocks

Posted on by
2

Recently I was irritated by the fact that Code::Blocks is not truly portable on Windows. Usually I keep two versions of Code::Blocks in my PC. One is the last released nightly and the other one is the one that I build from trunk. I use last released nightly to write code. However as Code::Blocks is not truly portable, these two versions of Code::Blocks share same configuration file.  Sometimes I run my newly built Code::Blocks from trunk, it crashes and corrupts my customised configuration file. And this irritates me a lot.

Other than this, you really can’t copy your configuration folder in a portable drive and expect entire Code::Blocks installation to behave as a truly portable software. There is one way; using personality feature of Code::Blocks. but that solves only one half of the problem. Yes, this makes your Code::Blocks portable. But your plugins are not! They still read their own settings from the default folder which is %APPDATA%CodeBlocks folder. Continue reading →