What Is The Minimum PC Requirement for codeblocks to run?

[SajibFinix]

Hi!
I want to know what is the minimum PC requirement for codeblocks to run.

[oBFusCATed]

A machine capable of running Windows XP and 512mb free ram after the OS has been started.
For linux is a similar...512mb free ram after the OS has been started.

[zabzonk]

You can get away with startlingly low spec machines. Up until last year, I was running C::B on a Windows 2K box with 256Mb total memory. It wasn't fast, but it did run with no problems. I don't believe more recent builds have greatly upped the system requirements.

[thomas]

I don't think there is a minimum requirement at all, other than screen size (with 800x600 or even smaller, it will look piss poor, and the settings dialogs probably won't fit on screen).

My copy of Code::Blocks has a virtual size of around 85-90 MiB and a working set of around 26-28 MiB (of which roughly 1/2 is mappings of system shared libraries, only 14 MiB are private).

Add a couple of megabytes depending on how big a project you want to load, and on how many editors you open at the same time. Obviously, keeping half a gigabyte worth of source files open in the editors will take (more than) half a gigabyte of memory, no surprise there.

A Windows system that can't make 15-20 MiB of physical memory available after boot is unusable. Launching Internet Exploder with an empty start page takes more than that, as do system tools like mmc.exe when you do anything but look at them. Windows Exploder dynamically allocates 40-60 MiB just for showing thumbnails when opening a folder with some images inside.

[oBFusCATed]

You can get away with startlingly low spec machines. Up until last year, I was running C::B on a Windows 2K box with 256Mb total memory. It wasn't fast, but it did run with no problems. I don't believe more recent builds have greatly upped the system requirements.

And what about the compiler and the linker?
Most of the time they are the memory eaters.

[zabzonk]

And what about the compiler and the linker?

Never had any problems building my projects - largest is is about 200 source and header files. As I said, it wasn't very fast, but I could still do a complete rebuild with no problems.
 

[oBFusCATed]

Neil: Do you use templates? If not, you've not seen what the compilers/linkers are capable in regard to memory eating

[zabzonk]

Neil: Do you use templates?

Of course I do! Is it really possible to use the C++ Standard Library without doing so? And I define a few of my own, too.

[thomas]

Compiler and linker may consume 50 MiB, with lots of template recursion I've seen 150-180 MiB.

A Windows operating system is running services that do nothing most of the time worth upwards of 200 MiB (and, usually, another 300-400 MiB of user/vendor installed crap). These will be swapped out when the compiler runs, so apart from a slight performance hit at the first moment, no problem there.

The only serious showstopper is LTO, which will not only quickly run out of physical memory on a low spec machine, but also regularly run out of address space under a 32 bit OS (with /3GB switch and a /LARGEADDRESSAWARE linker) --- LTO eats up the available 3 GiB like nothing.

[oBFusCATed]

LTO eats up the available 3 GiB like nothing.

And the sad thing is that it is slower at least for me:(

[DeeJayOne]

Hi everyone 

Is there a "Minimum System Requirements" section somewhere in the official documentation ? (for each version)

Regards

[blauzahn]

These are still fairly low and have not changed significantly over the years. See older posts. Of course, it depends on what order of magnitude the code you want to compile is. As a start, any 10 year old regular laptop/pc (running e.g Linux) or raspberry pi3 will do.