[M3devel] ROOT

[Tony Hosking]

I'm not talking about m3overrides.  That is a arguably a special- 
purpose hack.  We shouldn't layer a hack into the *normal* build  
process.


Antony Hosking | Associate Professor | Computer Science | Purdue  
University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484




On 2 Jul 2009, at 12:19, Jay wrote:

>
>> Seems broken to me to depend on
>> the source directory structure
>
> Like m3overrides? But yes, I agree.
> m3overrides seems broken too.
>
> - Jay
>
>
>
>
>
>
>
>
> ----------------------------------------
>> From: hosking at cs.purdue.edu
>> To: m3devel at elegosoft.com
>> Date: Thu, 2 Jul 2009 11:49:34 -0400
>> Subject: [M3devel] ROOT
>>
>> Where did variable ROOT come from? Do I really need to define it?
>> Seems broken to me to depend on the source directory structure as it
>> sets that structure in stone.
>>
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090702/ff4f2dd8/attachment-0002.html>