Curiously, why did we not (or have not yet) decided to use build.parallel to follow what seems to be a build.X pattern? Can build.jobs not take its place?

On Mar 18, 2009, at 10:10 PM, j...@macports.org wrote:

revision48314author...@macports.orgdate2009-03-18 19:10:17 -0700 (Wed, 18 Mar 2009)Log Message Make parallel build opt-out rather than opt-in (buildmakejobs still defaults to 1)
Modified Paths
        • trunk/base/src/port1.0/portbuild.tcl
Diff
Modified: trunk/base/src/port1.0/portbuild.tcl (48313 => 48314)
--- trunk/base/src/port1.0/portbuild.tcl 2009-03-19 00:52:26 UTC (rev 48313) +++ trunk/base/src/port1.0/portbuild.tcl 2009-03-19 02:10:17 UTC (rev 48314)
@@ -43,7 +43,8 @@
 options build.nice
 options build.jobs
 options build.asroot
-commands build parallel_build
+options use_parallel_build
+commands build
 # defaults
 default build.asroot no
 default build.dir {${workpath}/${worksrcdir}}
@@ -52,6 +53,7 @@
 default build.jobs {${buildmakejobs}}
 default build.pre_args {${build.target}}
 default build.target "all"
+default use_parallel_build yes

 set_ui_prefix

@@ -116,9 +118,9 @@
     # check if port allows a parallel build
     global use_parallel_build
     if {![tbool use_parallel_build]} {
+        ui_debug "port disallows a parallel build"
         return ""
     }
-    ui_debug "port allows a parallel build"

if {![exists build.jobs] || !([string match "*make*" [option build.cmd]] || [string match "*scons*" [option build.cmd]])} {
         return ""
_______________________________________________
macports-changes mailing list
macports-chan...@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-changes

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to