Opened 7 years ago

Closed 2 years ago

Last modified 2 years ago

#56435 closed enhancement (fixed)

selfupdate should use parallel build

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: jmroot (Joshua Root)
Priority: Normal Milestone: MacPorts 2.8.0
Component: base Version: 2.4.99
Keywords: Cc:
Port:

Description

Is there a good reason why selfupdate doesn't build MacPorts base in parallel?

Change History (4)

comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Assuming there isn't a good reason, we should make it build in parallel. Base has grown over the years, with bundled copies of other libraries, and now that Macs have more processor cores, parallel building can save a bit of time.

How should it be done? I hoped I could reuse the existing functionality in portbuild::build_getjobsarg but I assume most of that procedure (except the parts that check use_parallel_build and build.cmd), and all of portbuild::build_getjobs, should be moved into a file that's not meant to be specific to the port build phase. If so, where should it go? Into macports::? The tests will then need to be updated too, since they test those procedures.

comment:2 Changed 2 years ago by jmroot (Joshua Root)

Owner: set to jmroot
Resolution: fixed
Status: newclosed

In b98b7f18954db8ae630730b1429878dae07f3002/macports-base (master):

Obey buildmakejobs in selfupdate

Closes: #56435

comment:3 Changed 2 years ago by jmroot (Joshua Root)

Milestone: MacPorts Future

comment:4 Changed 2 years ago by jmroot (Joshua Root)

Milestone: MacPorts FutureMacPorts 2.8.0
Note: See TracTickets for help on using tickets.