Default compiler suite (was Re:[28325] trunk/dports/graphics/wxWidgets-devel/Portfile)

[Weissmann Markus]

On 03.09.2007, at 02:43, Ryan Schmidt wrote:

>
> On Sep 2, 2007, at 12:11, Weissmann Markus wrote:
>
>> On 01.09.2007, at 22:52, Ryan Schmidt wrote:
>>
>>> On Sep 1, 2007, at 12:45, Landon Fuller wrote:
>>>
>>>> On Sep 1, 2007, at 6:07 AM, Weissmann Markus wrote:
>>>>
>>>>> 'portconfigure.tcl' from trunk will chose a default for darwin  
>>>>> 7/8/9 (gcc3.3/4.0/4.0). Please test it! Just replacing /opt/ 
>>>>> local/share/macports/Tcl/port1.0/portconfigure.tcl with http:// 
>>>>> svn.macports.org/repository/macports/trunk/base/src/port1.0/ 
>>>>> portconfigure.tcl manually should do the trick.
>>>>>
>>>>> This version also fixes a bug that when using  
>>>>> configure.compiler every user-added compiler selection (e.g.  
>>>>> 'configure.cc /bin/true') was overwritten.
>>>>
>>>> This is going to break ports that require a different compiler,  
>>>> but specify the compiler using configure.env, or arguments to  
>>>> configure via configure.args.
>>>
>>> Then we should start cleaning ports. All those that specify a  
>>> different compiler via configure.env should be updated to use  
>>> configure.cc, etc. Those that use configure.args (or build.args  
>>> I've also seen) should... I don't know, be tested to see if they  
>>> can instead use configure.cc (or build.cc, etc.; do we have that?).
>>
>> Indeed. "configure.env" is not officially supported anymore  
>> anyway... some ports cant do without, but most can. Please  
>> everybody clean your ports.
>
> Why isn't configure.env supported anymore?
>

oops - sorry, my fault! I really wanted to say:
Using configure.env directly should be avoided - we do have a nice  
set of commands for setting the most used flags at configuration  
time. If you cannot do without, of course it is still supported.


> The new guide documents this option, and does not mention anything  
> about it being deprecated or unsupported. If it is unsupported, the  
> guide should state that, and recommend alternatives.
>
> http://geeklair.net/new_macports_guide/#reference.keywords.configure
>

Well yes. We should probably though put our manpages online, too and  
clearly state that if in doubt the manpage is right.


-Markus

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