Thanks! I like this option for those builds I do as a one-off. Comer
On Wednesday, May 25, 2016, Adam Dershowitz <[email protected]> wrote: > > > > On May 25, 2016, at 5:25 PM, Brandon Allbery <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > > On Wed, May 25, 2016 at 5:22 PM, Christopher Jones < > [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> 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. >
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
