Forum: IronRuby Building IronRuby

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
573b9499030e1ccb867ef80f0ff1ac49?d=identicon&s=25 Justin Bailey (Guest)
on 2009-01-23 02:16
(Received via mailing list)
I've just gotten the latest ironruby bits from github and cannot
build. Using Merlin\Main\Languagues\Ruby\IronRuby.sln:

  * Can't open the Microsoft.Scripting project because it imports from
"Merlin\Main\Support\SpecSharp.targets" which is not in the repo.
  * Cryptographic failures when building because
"Support\MSSharedLibKey.snk" does not exist.

Removing the import statement from
and creating a fake SNK file in the appropriate directory lets me get
further, but I still can't build:

  * 'IronRuby.Compiler.Methods' is inaccessible due to its protection
29  77

  * 'IronRuby.Runtime.Calls.BlockDispatcher' does not contain a
definition for 'MaxBlockArity'
102  59

Basically a bunch of internal definitions look like they should be
public. Am I missing something or did a bad commit slip through?

Ade8632553a9243ae05fc920f68644c1?d=identicon&s=25 Jim Deville (Guest)
on 2009-01-23 03:07
(Received via mailing list)
Can you try command line? From Merlin\Main\Languages\Ruby, run "set
MERLIN_ROOT=Path\To\Merlin\Main", then run "rake compile". I will try to
have SpecSharp.targets moved in the next couple of pushes.

Tomas: Do we still need the second copy of SpecSharp.targets in
Merlin/Main/Languages/Ruby? Also, can I delete IronRuby.sln (leaving
only Ruby.sln). If we don't need the SpecSharp.targets, I'll move it
from Support back to Main, delete the one in Ruby and update references.

E1deaac6561498a0e7472e6268ea9ccc?d=identicon&s=25 Jimmy Schementi (Guest)
on 2009-01-23 04:13
(Received via mailing list)
FYI, Jim (I believe) and I are starting to work out of Git primarily, so
we'll be forced to iron out these kinks. Also, preserving commit
information between git and tfs is a goal, so no more of the "sync with
tfs" commits ... you'll see the actual msg/author ... and we'll have to
get a reliable continuous integration server.

Just a heads up that though it's painful now, it's going to get much
better soon, and everyone to be on the same playing field.

573b9499030e1ccb867ef80f0ff1ac49?d=identicon&s=25 Justin Bailey (Guest)
on 2009-01-23 18:55
(Received via mailing list)
Thanks for the hint - I am able to build from the command line.
This topic is locked and can not be replied to.