custom makefile support mutliple cpus

[mattn2]

Hi,

we are looking for a way to get the amount of cpus in a codeblocks variable that can be used in the custom makefile parameters

something like:

$make -r -R -j $cpus -f $makefile $target

is something like this available?

thanks a lot
martin

[dmoore]

I think per project variables is what you are looking for.

[Jenna]

Hi,

we are looking for a way to get the amount of cpus in a codeblocks variable that can be used in the custom makefile parameters

something like:

$make -r -R -j $cpus -f $makefile $target

is something like this available?

thanks a lot
martin

On linux you should be able to use something like (note the backticks):

$make -r -R -j `getconf _NPROCESSORS_ONLN` -f $makefile $target

[dmoore]

Isn't it a bit odd that a compiler that supports multiple CPUs doesn't have a switch to detect the number of CPUs?

[mattn2]

it's not the compiler, but make

on windows i could also use the env var %NUMBER_OF_PROCESSORS% - but i'm looking for a portable way to handle this.

[Jenna]

You could try something like:

$make -r -R -j $if(PLATFORM == PLATFORM_MSW){%NUMBER_OF_PROCESSORS%}{`getconf _NPROCESSORS_ONLN`} -f $makefile $target

the linux part should work, but I'm not sure about the windows part, you might need someting similar to linux' "echo".

[mattn2]

thanks - but there is also mac - which does this again a little bit different. and c::b must already know the amount of cpus, no?

[Jenna]

wxWidgets has a static function to determine the umber of cpu's, but I don't know how good it works.
But it could surely be used to add a cpu_count macro, that can be used wherever macro-/variable-expansion is done.

[oBFusCATed]

wxWidgets has a static function to determine the umber of cpu's, but I don't know how good it works.
But it could surely be used to add a cpu_count macro, that can be used wherever macro-/variable-expansion is done.

We have also a setting for the number of cpus used for building, this could be provided here.

[Jenna]

wxWidgets has a static function to determine the umber of cpu's, but I don't know how good it works.
But it could surely be used to add a cpu_count macro, that can be used wherever macro-/variable-expansion is done.

We have also a setting for the number of cpus used for building, this could be provided here.

Both could be provided:
the number of CPU's determined by wxw and the number of parallel processes for building set by the user in the compiler options dialog.

[MortenMacFly]

wxWidgets has a static function to determine the umber of cpu's, but I don't know how good it works.

It works pretty well - I am using it in another of my projects (You meant the static wxThread based method, right?)

[Jenna]

wxWidgets has a static function to determine the umber of cpu's, but I don't know how good it works.

It works pretty well - I am using it in another of my projects (You meant the static wxThread based method, right?)

Yes

[MortenMacFly]

Yes

Reminds me: Recently had the chance to work on a 16 core "enterprise PC". What a mind-blowing fast compilation of everything you do there with C::B, having setup 16 parallel build processes. Also, the wxThread methods worked fine there, too. Now all I need is somebody giving me enough money because I want to have such a beast, too. :-)

[Jenna]

Yes

Reminds me: Recently had the chance to work on a 16 core "enterprise PC". What a mind-blowing fast compilation of everything you do there with C::B, having setup 16 parallel build processes. Also, the wxThread methods worked fine there, too. Now all I need is somebody giving me enough money because I want to have such a beast, too. :-)

That's more or least what I need too, with at least 32 GB of Ram.

An alternative would be a quadcore laptop with 32 GB installable Ram.

[oBFusCATed]

Moar cores, moar...

Jen: why would you need so much ram? ;D