[Ironruby-core] Compiling on Mono?

Michael Letterle michael.letterle at gmail.com
Mon Oct 25 16:55:25 EDT 2010


Well, some of us don't need the CI server as we're programming against
mono already ;)

FWIW, I'm looking into getting the linux CI server back up and running
with CJ's help.

But agreed. I can back out the ifdef I made and just use the work around.

Also, should we be targeting a specific version of mono, or just
trunk?  Something else to think about.... historically I always used
trunk to allow mono to "catch up" as far as possible since the
majority of work was done against .NET... it seems this might be a
good chance to change that disconnect.

On Mon, Oct 25, 2010 at 4:18 PM, Tomas Matousek
<Tomas.Matousek at microsoft.com> wrote:
> Once we'll have CI server test against Mono we'll discover the problem right away and don't check in anything that would be broken on Mono.
> I suggest we implement the workaround, file bugs into Mono and IronRuby bug trackers, and add a comment to the code with explanation and a link to the filed IronRuby bug. When the bug is fixed in Mono we go and remove the workaround to keep the code base clean.
>
> Tomas
>
> -----Original Message-----
> From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Michael Letterle
> Sent: Monday, October 25, 2010 12:10 PM
> To: ironruby-core at rubyforge.org
> Subject: Re: [Ironruby-core] Compiling on Mono?
>
> How do we want to handle things that CAN be worked around in Mono before they're patched then?
>
> I agree that the same binaries should run in either location, but Mono necessarily is always playing catchup.
>
> Unless we target Mono.... >.>
>
> On Mon, Oct 25, 2010 at 1:30 PM, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote:
>> I think we should not have any #if MONO conditionals. That would mean
>> we'd need a different set of binaries for Mono, Moonlight, etc. almost
>> doubling the number of flavors we have today (desktop CLR, Silverlight
>> 4, Silverlight 3).
>>
>> Now that Mono 2.8 is released we can use memory mapped files (it
>> wasn't available when I wrote this code). We don't need to use P/Invokes anymore.
>>  I have the V4 implementation somewhere almost working so I might be
>> able to check it in soon.
>>
>>
>>
>> Tomas
>>
>>
>>
>> From: ironruby-core-bounces at rubyforge.org
>> [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Andrius
>> Bentkus
>> Sent: Monday, October 25, 2010 10:12 AM
>>
>> To: ironruby-core at rubyforge.org
>> Subject: Re: [Ironruby-core] Compiling on Mono?
>>
>>
>>
>>
>>
>> On Mon, Oct 25, 2010 at 2:51 PM, Joe Scott <joseph_scott123 at msn.com> wrote:
>>
>> Doing a google search I found this.
>>
>> I have not had a chance to try it out maybe this would work.
>>
>> http://groups.google.com/group/DotNetDevelopment/msg/ba5e2bd42ecb83e3
>>
>>
>>
>> It is really possible, I guess I was too lazy to do the search myself,
>> thanks for googling :)
>>
>>
>>
>>
>>
>> ________________________________
>>
>> Date: Mon, 25 Oct 2010 12:31:08 +0200
>> From: Andrius.Bentkus at rwth-aachen.de
>> To: ironruby-core at rubyforge.org
>> Subject: Re: [Ironruby-core] Compiling on Mono?
>>
>>
>>
>> On Mon, Oct 25, 2010 at 11:23 AM, Alistair Bush <ali_bush at gentoo.org> wrote:
>>
>>> I got it compiling, there is a missing reference for Mono.Posix, one
>>> bad cast and you need to use CCI in the constants. Does someone know
>>> what CCI should be?
>>
>> patches would be nice :)
>>
>>
>>
>> I can't patch the csproj with the missing reference because it would
>> break building on windows. Creating another set of csproj for the a
>> mono build would be madness. Do csproj'ects support something like
>> ifdef or is it possible to include a reference only when mono is used?
>>
>> And the other change I made was a one liner, I don't think that
>> attaching an entire patch is is really necessary for it. Just run
>> xbuild with CCI: xbuild /property:TreatWarningsAsErrors=false /property:DefineConstants="DEBUG MONO"
>> Ruby.csproj
>>
>> and look at the warning outputs... O for god sake, I'll just attach it.
>> I used this branch: http://github.com/mletterle/ironruby/tree/linux as
>> the base.
>>
>>
>>
>> _______________________________________________ Ironruby-core mailing
>> list Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
>> _______________________________________________
>> Ironruby-core mailing list
>> Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
>> There is just another question, maybe one of the former developers
>> will know, why are there 2 build systems now? Why is there a
>> *.build.csproj for every *.csproj? Isn't that redudant like the suggested rakefiles?
>>
>> _______________________________________________
>> Ironruby-core mailing list
>> Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
>>
>
>
>
> --
> Michael Letterle
> IronRuby MVP
> http://blog.prokrams.com
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>



-- 
Michael Letterle
IronRuby MVP
http://blog.prokrams.com


More information about the Ironruby-core mailing list