[28660] trunk/base/src/port1.0/portbuild.tcl

[Weissmann Markus]

While thinking about it: Wouldn't it be best in the case of a given  
build-style to use the full path to the chosen tool? Like "/usr/bin/ 
bsdmake" etc.
else there could be nasty conflicts with ports not naming their  
executables exactly like the platform does (which at least is the  
case on different operating systems than OS X).


-Markus

On 06.09.2007, at 12:28, source_changes at macosforge.org wrote:

> Revision 28660 Author afb at macports.org Date 2007-09-06 03:28:48  
> -0700 (Thu, 06 Sep 2007) Log Message fix gnu/bsd make defaults  
> Modified Paths
> trunk/base/src/port1.0/portbuild.tcl
> Diff
> Modified: trunk/base/src/port1.0/portbuild.tcl (28659 => 28660) ---  
> trunk/base/src/port1.0/portbuild.tcl	2007-09-06 10:07:07 UTC (rev  
> 28659) +++ trunk/base/src/port1.0/portbuild.tcl	2007-09-06 10:28:48  
> UTC (rev 28660) @@ -61,13 +61,17 @@ bsd { if {[option os.platform]  
> == "darwin"} { return bsdmake +	 } elseif {[option os.platform] ==  
> "freebsd"} { +	 return make } else { -	 return make +	 return  
> pmake } } gnu { if {[option os.platform] == "darwin"} { return  
> gnumake +	 } elseif {[option os.platform] == "linux"} { +	 return  
> make } else { return gmake }
> _______________________________________________
> macports-changes mailing list
> macports-changes at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-changes

---
Markus W. Weissmann
http://www.mweissmann.de/