According to MoMA, there are over 40 red flags between the IPY dlls and the DLR (Microsoft Scripting) dlls. One of them has 2 P\Invokes that it doesn't like and the others are a mix of TODOs on the mono side, or not-implementeds.
Another block (for me) is that Mono doesn't implement the following method: AppDomain AppDomain.CreateDomain (string, Evidence, AppDomainSetup, PermissionSet, StrongName[]) Though for the latter I'm sure theres a long way to accomplish the same thing. It seems moot anyway, since IPY2 will not run as-is yet. I'm sure it will be better as Mono keeps on maturing. On Fri, Feb 20, 2009 at 1:27 PM, Douglas S. Blank <dbl...@brynmawr.edu>wrote: > Doug Blank wrote: > >> Now that IronPython2 is out, wondering about IronPython on Mono... >> >> Seo Sanghyeon-3 wrote: >> >>> Currently you need Mono SVN (both to run and to compile). Using SVN >>> r120972 below. >>> >> >> Any idea what version of Mono that is? Does IP2 build with Mono 2.2? It >> would be great to put out a IPCE r8 for IP2. >> >> Also, what would be the matching versions of IronRuby that would work with >> IP on Mono? I see that DevHawk has a DLR nightly build that comes with >> Ruby >> and Python: >> >> http://nightlybuilds.cloudapp.net/rss.ashx?project=dlr >> >> but the early builds seem to be empty (I've sent Harry a note about that). >> The latest versions of those builds don't quite work with Mono 2.0, but >> perhaps Mono 2.2? >> > > Answering part of my own question: Mono 2.2 that comes with OpenSuse is not > capable of running the IP from the DLR nightly builds, versions 10209 and > later (earlier versions are unavailable there). > > So, I'm still in quest of a IP/IR combo that I can run on mono. I will try > building mono from SVN next... > > -Doug > > > Thanks for any assistance! >> >> -Doug >> >> >> Seo Sanghyeon-3 wrote: >> >>> The binary runs fine. >>> >>> IronPython includes its own copy of ExtensionAttribute, but this >>> doesn't seem to work with Mono C# compiler: that is, extension methods >>> don't get recognized as extension methods. This causes trouble where >>> MetaObject is defined in Microsoft.Scripting.Core.dll, and its >>> extensions are defined in MetaObjectExtensions in >>> Microsoft.Scripting.dll. My hack below copies MetaObjectExtensions and >>> its dependencies to Microsoft.Scripting.Core and patch it to be a >>> partial class instead of a static class housing extension methods. Any >>> better idea? >>> >>> Also there are some unused files in the source distribution. >>> >>> Below are steps I used to compile the source on Mono. >>> >>> Download source from >>> >>> http://www.codeplex.com/IronPython/Release/ProjectReleases.aspx?ReleaseId=19841 >>> $ unzip IronPython-2.0-Src.zip >>> $ cd IronPython-2.0 >>> >>> Some hacks... >>> $ svn co -r 597 >>> https://fepy.svn.sourceforge.net/svnroot/fepy/trunk/patches/latest >>> build >>> >>> This deletes unused files and does copying mentioned above >>> $ sh build/pre.sh >>> >>> Copies NAnt build file: it uses noconfig to avoid pulling System.Core.dll >>> $ cp build/IronPython.build Src >>> >>> Patches >>> $ patch -p1 < build/patch-exthack >>> $ patch -p1 < build/patch-console >>> >>> Build >>> $ cd Src >>> $ nant >>> >>> -- >>> Seo Sanghyeon >>> _______________________________________________ >>> Users mailing list >>> Users@lists.ironpython.com >>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com >>> >>> >>> >> > > -- > Douglas S. Blank > Director, Institute for Personal Robots in Education (IPRE) > http://www.roboteducation.org > Chair, and Associate Professor, Computer Science, Bryn Mawr College > http://cs.brynmawr.edu/~dblank <http://cs.brynmawr.edu/%7Edblank> > (610)526-6501 > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com >
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com