[MonoDevelop] Autotools integration?

Ian MacLean ianm@ActiveState.com
Thu, 16 Dec 2004 01:56:31 +0900


Michael Lausch wrote:

>On Wed, 2004-12-15 at 04:56 -0800, Peter Johanson wrote:
>  
>
>>On Wed, Dec 15, 2004 at 10:02:37AM +0100, Michael Lausch wrote:
>>    
>>
>>>On Tue, 2004-12-14 at 21:47 -0800, Todd Berman wrote:
>>>      
>>>
>>>>On Tue, 2004-12-14 at 21:13 -0500, Miguel de Icaza wrote:
>>>>        
>>>>
>>>>>    Hence organically grown, pkg-config based, and the configure and
>>>>>Makefiles generated from our internal XML "Solution" format is the right
>>>>>path to go.
>>>>>
>>>>>Miguel.
>>>>>          
>>>>>
>>>>There is already the beginnings of an implementation of this in
>>>>MonoDevelop. However, to not conflict with existing makefiles, the
>>>>makefile created is named Makefile.SolutionName and is easily runnable
>>>>via a make.sh file created in your toplevel directory.
>>>>        
>>>>
>>>and using NAnt for this? the advantage of NAnt is that it's easier to
>>>      
>>>
>>See the previous statement about NAnt being more than non-trivial to get
>>installed/working currently.
>>    
>>
>
>the current rc1 release has exacvtly two issues, with respect to mono.
>one is a trivial reordering in the config file, to bring the runtime
>requirements in the "correct" order, the other is a compiler issue (i
>assume), which can be resolved by a trivial patch. 
>
strictly speaking these are issues with current mono svn that nant 
happens to run into. The config file issue is I think because of this bug:

http://bugzilla.ximian.com/show_bug.cgi?id=62913
where the 2.0 profile is assumed even if it hasn't been installed.


The compiler issue is the one you get when compiling NDocTask.cs ? That 
is a bug in mcs where it confuses a property named "Project" with a 
class called "Project". I've been meaning to log it in bugzilla just as 
soon as I get a simple test case together. btw your nant-ndoc-task.patch 
[1] workaround would be a lot simpler by changing:

attr.Value = Project.ExpandProperties(attr.Value, Location); to 
attr.Value = this.Project.ExpandProperties(attr.Value, Location);

rather than fully qualifying every reference to a NDoc type.

Ian

[1] 
https://www.lausch.at/svn/public/monodevelop/nantplugin/trunk/nant-ndoc-task.patch