use of cpus in building

[Comer Duncan]

Thanks! I like this option for those builds I do as a one-off.

Comer

On Wednesday, May 25, 2016, Adam Dershowitz <dersh at alum.mit.edu> wrote:

>
>
>
> On May 25, 2016, at 5:25 PM, Brandon Allbery <allbery.b at gmail.com
> <javascript:_e(%7B%7D,'cvml','allbery.b at gmail.com');>> wrote:
>
> On Wed, May 25, 2016 at 5:22 PM, Christopher Jones <
> jonesc at hep.phy.cam.ac.uk
> <javascript:_e(%7B%7D,'cvml','jonesc at hep.phy.cam.ac.uk');>> wrote:
>>
>> you don’t. Its automatic for the ports that allow it.
>
>
> And this is also true, if that was not clear. Using multiple cores is *on
> by default*. You are already getting it, unless you at some point in the
> past overrode buildmakejobs in macports.conf.
>
> --
>
>
>
> You can also manually change it for a single install, for example by using
> build.jobs.  Such as:
> sudo port install port_whatever_name build.jobs=4
> and then, for that specific install it will attempt to use 4 cores.  This
> can be handy to reduce the number of cores used, from the default, so that
> you can do other things on the machine while building.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20160525/65319226/attachment.html>