Clerical Rigor

More DLR work

Ivan put up a hudson server on our winders box. Ankit helped me figure out the IronRuby xbuild build problems. I should probably try it on IronPython, too. I sent the ironruby-core list a patch to fix some case sensitivity issues. Some time in the near future, I’m going to get together a bug report for the compiler and send it off to Marek. But I’m tired and Scarlet’s got a friend doing the sleep-over thing tonight.

So. Later ;)

P.S., can you believe that nobody registered a11y.com before now? Crazy talk.

P.P.S., does anyone out there in gnome land have a ruby app they want to test for compatibility with IronRuby?

C.J. Collier

, , , , , , , , , , ,

5 responses to “More DLR work”

  1. C.J., I’m trying to do the same with the Codeplex DLR package and mono trunk (version 2.7 r154753):

    http://dlr.codeplex.com/releases/view/34834

    But have hit some snags. Two were fixed with moves:

    mv Codeplex-DLR-0.92/Src/Languages/Ruby/ironruby Codeplex-DLR-0.92/Src/Languages/Ruby/IronRuby
    mv Codeplex-DLR-0.92/Src/Languages/Ruby/yaml Codeplex-DLR-0.92/Src/Languages/Ruby/Yaml

    I also removed the Chiron project from the toplevel sln. But encounter some syntax errors, like:

    Ast/ElementInit.cs(108,35): error CS1584: XML comment on `Microsoft.Scripting.Ast.Expression.ElementInit(System.Reflection.MethodInfo, System.Collections.Generic.IEnumerable)’ has syntactically incorrect cref attribute `IEnumerable{T}’

    Any ideas?

    Reply

    • Hey there. I’ve been able to get it building with mono from trunk by using Ivan’s patches. He’s got them in his repo over at git://github.com/casualjim/ironruby.git on the linux branch. It looks like you discovered the .target issue. Ankit tells me that he’ll have a patch in trunk by Wednesday or so to resolve that issue. Until then, as you discovered, you can resolve the issue by copying the .targets and .tasks files from the 4.0 profile to the 2.0 profile.

      Just to let you know, /usr/local is probably not the best place to put your parallel install of mono.

      http://www.mono-project.com/Parallel_Mono_Environments

      Cheers,

      C.J.

      Reply

      • Thanks for the feedback (and hint about /usr/local … that may explain some things over the years!)

        Note that I’m using the Codeplex DLR package, which includes Ruby and Python, but may be different from the separate Ruby and Python packages. (I really want to have Ruby and Python interoperating).

        So, I understand you that some of these issues will be fixed in mono trunk soon. But it looked like some of the changes in the github are changes to Ruby code from MS. Is mono maintaining their own versions of MS code, or am I just mistaken?

        Thanks again!

        Reply

        • I would recommend using Ivan’s github repo. It has IronRuby, IronPython and the DLR. It’s what I’m using to build the next Debian package. It will allow Ruby and Python to inter-operate.

          Mono proper is not involved with IronRuby/IronPython/the DLR. A bunch of Mono contributors are working on it, though, so I guess one might consider this to be the same thing. But in any case, Ivan is maintaining patches against the MS repo. MS doesn’t allow patches to the core of IR or IPy, so we need to keep our own branches until the changes we fix get addressed upstream.

          We’re over on #IronRuby and #IronPython on freenode if you want more real-time responses. I’ve seen you on IRC before, haven’t I?

          Cheers,

          C.J.

          Reply

  2. I also forgot: I had to copy a couple of missing targets:

    cp /usr/lib/mono/2.0/Microsoft.CSharp.targets /usr/local/lib/mono/2.0/
    cp /usr/lib/mono/2.0/Microsoft.Common.ta* /usr/local/lib/mono/2.0/

    I also tried the DLR trunk, and got the same error. Perhaps these targets are incorrect?

    Reply

Leave a Reply