I have to respecify DEBUG since I'm redefining the DefineConstants property.
Running would have worked as long as you didn't try to call that method :) On Sat, Oct 23, 2010 at 12:29 PM, Tomas Matousek <tomas.matou...@microsoft.com> wrote: > I see. "DEBUG" seems to be redundant since it's set by the default Debug > configuration in the project files. > Strange, I think I tried running IronRuby on Mono 2.8 and most of it worked. > If TryEnter implementation was missing something should have failed. But this > was compiled using our compiler not Mono's. So maybe the problem is just at > build time? > > We should work with JB to get any issues fixed. > > Tomas > > -----Original Message----- > From: ironruby-core-boun...@rubyforge.org > [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Michael Letterle > Sent: Saturday, October 23, 2010 4:03 AM > To: ironruby-core@rubyforge.org > Subject: Re: [Ironruby-core] Contributing? > > Well, it's just the DEBUG constant and a MONO constant. > > I'm building with mono trunk, I added the MONO to the ifdef to use the > Monitor.TryEnter(object) overload that is also used for CLR2. I couldn't > just use the CLR2 constant because that broke everything else. I'm going to > look into adding the Monitor.TryEnter(object, > bool) overloads to mono proper so this is just temporary. > > > > On Sat, Oct 23, 2010 at 3:19 AM, Tomas Matousek > <tomas.matou...@microsoft.com> wrote: >> What do you need the "DEBUG MONO" constant for? The default "Debug" >> configuration doesn't work? >> >> What version of Mono do you use? I think 2.8 should be the target for >> IronRUby. >> >> Tomas >> >> -----Original Message----- >> From: ironruby-core-boun...@rubyforge.org >> [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Michael >> Letterle >> Sent: Friday, October 22, 2010 8:02 PM >> To: ironruby-core@rubyforge.org >> Subject: Re: [Ironruby-core] Contributing? >> >> Along the lines of IronRuby on mono, a small change was required for now >> since Mono doesn't implement one of the newer Monitor.TryEnter overloads, >> see my branch here: >> http://github.com/mletterle/ironruby/tree/linux >> >> compiles with: >> >> xbuild /property:TreatWarningsAsErrors=false >> /property:DefineConstants="DEBUG MONO" Ruby.csproj >> >> Working on getting IronRuby.Console compiled now... already ran into a >> casing issue >.< >> >> On Fri, Oct 22, 2010 at 9:02 PM, Jonathan Allen <grauenw...@gmail.com> wrote: >>> I would caution you against moving too far away from Microsoft >>> Technology, lest you alienate Windows developers. >>> >>> 1. If this project is going to be owned by Mono, then it would be >>> reasonable to move to GitHub. But to drop CodePlex just because you >>> feel like being stubborn isn't. >>> >>> 3. One of the biggest barriers for Windows developers who want to >>> contribute to Mono is the project/build system. When looking at it >>> for the first time it is really hard to just figure out where to start. >>> And they certainly don't want to go back to editing source files with >>> notepad. So while being able to build without Visual Studio is >>> important, be careful not to remove the VS/MSBuild option. >>> >>> >>> Jonathan Allen >>> >>> On Fri, Oct 22, 2010 at 5:10 PM, Mike Moore <blowm...@gmail.com> wrote: >>>> >>>> With a brave new world ahead for IronRuby, what do you all think >>>> about the following ideas? >>>> 1) Move to GitHub - I won't likely contribute if I have to use CodePlex. >>>> And I'd like to contribute. Can we do like the rest of Mono and make >>>> GitHub the central repository and source of all truth? Please? >>>> 2) Detach IronPython - Looking through the code, it seems that >>>> IronPython is in the same repo. I'm sure this is a holdover of how >>>> Microsoft had everything organized. And I'm sure it made sense then, >>>> but I don't think it makes sense now. I'd like to work on IronRuby, >>>> and I honestly don't care about having to check IronPython. Now that >>>> the DLR API is fixed, and there is no longer one Microsoft group in >>>> charge of both projects, can we move these into separate repos? >>>> 3) Detach from Visual Studio - I'm not on Windows, and I won't be >>>> using Visual Studio. I'd prefer everything to build with rake tasks >>>> on Windows and Mono. I assume things are the way they are right now >>>> because of Microsoft's build process. And right now it does not seem >>>> possible for me to build without Visual Studio. What about devs who >>>> are using MonoDevelop? Or any of the more powerful text editors? I'm >>>> convinced this is a major hurdle to getting many of the other >>>> Rubyist language implementors involved. Assuming I am not alone on >>>> this, is it possible we can make this project reflect the realities of the >>>> majority of folks that would like to contribute? >>>> 4) Remove ancillary projects into their own repos - IronRuby.Rack >>>> should live in its own repo, IMO. So should the Visual Studio tools. >>>> This is similar to separating IronPython into its own repo, but it >>>> needs to go further. Are there any reasons this should not be done? >>>> What else do you guys think needs to change now that IronRuby is >>>> free from Microsoft's processes? >>>> _______________________________________________ >>>> Ironruby-core mailing list >>>> Ironruby-core@rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/ironruby-core >>>> >>> >>> >>> >>> -- >>> Jonathan Allen >>> 619-933-8527 >>> >>> _______________________________________________ >>> Ironruby-core mailing list >>> Ironruby-core@rubyforge.org >>> http://rubyforge.org/mailman/listinfo/ironruby-core >>> >>> >> >> >> >> -- >> Michael Letterle >> IronRuby MVP >> http://blog.prokrams.com >> _______________________________________________ >> Ironruby-core mailing list >> Ironruby-core@rubyforge.org >> http://rubyforge.org/mailman/listinfo/ironruby-core >> >> _______________________________________________ >> Ironruby-core mailing list >> Ironruby-core@rubyforge.org >> http://rubyforge.org/mailman/listinfo/ironruby-core >> > > > > -- > Michael Letterle > IronRuby MVP > http://blog.prokrams.com > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > -- Michael Letterle IronRuby MVP http://blog.prokrams.com _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
