As some of you may know, IronPython team has an internal repository for development, and this repository is pushed to CodePlex with help of the script. When DLR-based IronPython 2.0 Alpha 1 came out, this script stopped working and no new changes appeared on CodePlex.
Thanks to Ryan Dawson, this problem seems to be fixed now. (Kudos for prompt action!) One of the big change is the removal of Microsoft.Scripting.Vestigial.dll, as expected. This is a good thing, but it also means I need to modify my Makefile. Makefile for IronPython 2.0 is already annoying because of hacks I had to put there to handle resource files compilation. So I decided to investigate the alternative. NAnt is a free build tool for .NET which works with Microsoft .NET Framework as weel as with Mono. I'm not a big fan of XML, but it does handle resource files compilation out of the box. I also think NAnt is ridiculously overpowered for the task at hand, but so is GNU Make... I started reading User Manual and it turned out to be pretty simple. Here you see NAnt build file for IronPython 2.0 Alpha 1: http://fepy.svn.sourceforge.net/viewvc/fepy?view=rev&revision=493 And here is NAnt build file for the latest source from CodePlex. Note the text changed, which clearly shows what was removed. It isn't too clear with Makefile. http://fepy.svn.sourceforge.net/viewvc/fepy?view=rev&revision=495 I want to stop maintaining Makefile and switch to NAnt. If you don't want that please speak up. To IronPython team: would it be possible to have NAnt build support in the release from Microsoft? Persumably this would help projects already using NAnt and considering using IronPython. -- Seo Sanghyeon _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
