Build issues?

Am I the only one having issues building the current IronRuby/DLR code?

Some of the issues I’ve noticed:

1- “rake compile” seems to brake for me always, because it deletes the
output directory first but doesn’t recreate it, and then the
compilation for the resources in Microsoft.Scripting.dll breaks
because of it.

2- Manually creating the output directory and then doing “rake
compile_dlr” followed by “rake compile_ruby” works around the issue.
But, that brings me to another point: There doesn’t seem to be a rake
option to build IronRuby.Libraries!

3- Building using msbuild… not working so well, either, as some of
the projects still seem to have project references that use the old
directory names…

Tomas R.:

compile_dlr" followed by “rake compile_ruby” works around the issue.
But, that brings me to another point: There doesn’t seem to be a rake
option to build IronRuby.Libraries!

Umm … rake compile_libraries?

Smells like you have an older version of the Rakefile there?

3- Building using msbuild… not working so well, either, as some of
the projects still seem to have project references that use the old
directory names…

You’ll need to use the IronRuby.sln solution and not Ruby.sln. This runs
fine here:

msbuild /p:Configuration=“Debug” IronRuby.sln

-John

I was able to build by setting the solution configuration to
ExternalDebug and then building.

As for rake, I needed to do this first:

gem install pathname2

Then when I did rake compile, I got some runtime error in rake. :frowning:

Building from VS seemed to work for me.

Phil

Hi John!

Umm … rake compile_libraries?

Ahh, thanks, that works. Then the problem is that it is not listed in
the help when you just hit rake alongside the other options.

You’ll need to use the IronRuby.sln solution and not Ruby.sln. This runs fine here:

msbuild /p:Configuration=“Debug” IronRuby.sln

Nope, doesn’t work here. It breaks when compiling Ruby.csproj with a
bunch of missing references errors. (the DLR builds fine, but the
IronRuby project can’t find it, and same for the libraries project).

I did do yet another svn update just in case.

Tomas R.:

You’ll need to use the IronRuby.sln solution and not Ruby.sln. This
runs fine here:

msbuild /p:Configuration=“Debug” IronRuby.sln

Nope, doesn’t work here. It breaks when compiling Ruby.csproj with a
bunch of missing references errors. (the DLR builds fine, but the
IronRuby project can’t find it, and same for the libraries project).

I just deleted my svn directory and re-synced with r65. MSBuild it blew
up the first time I ran it, but then it compiled fine the second time
around. It looks like something might be screwed up with build ordering.

Does rake compile still fail out of the box with r65?

If you can mail a text dump of the build output that will be helpful in
diagnosing what might be busted.

Thanks,
-John

    Done building target "ResolveProjectReferences" in project

the namespace ‘Microsoft’ (are you missing an assembly reference?)

and a lot more after that.

Can you send me a copy of your ruby.csproj (off list is fine). It seems
like you’ve got a borked copy of ruby.csproj, but I want to confirm
this.

Also, have you tried to dump the svn repository into some other fresh
directory on your machine and building there?

Thanks,
-John

Can you send me a copy of your ruby.csproj (off list is fine). It seems like you’ve got a borked copy of ruby.csproj, but I want to confirm this.

Done. Thanks.

Also, have you tried to dump the svn repository into some other fresh directory on your machine and building there?

Yep. Just deleted the whole tree and got it fresh from SVN and got the
exact same error.

Hey John,

Does rake compile still fail out of the box with r65?

Weird, tried it again and seems to be working now (though svn didn’t
update anything this time).

As for the msbuild file, running it multiple times doesn’t seem to do
the trick. It goes something like this:

    __________________________________________________
    Project "E:\Opensource\ironruby\trunk\IronRuby.sln" is

building “E:\Opensource\ironruby\trunk\src\ironruby\Ruby.csproj”
(default targets):

    Target ResolveProjectReferences:
        C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets

: warning : The referenced project
‘…\Runtime\Microsoft.Scripting\Microsoft.Scripting.csproj’ does
not exist.
Done building target “ResolveProjectReferences” in project
“Ruby.csproj”.
Target CoreCompile:
<bunch of .cs files listed>
Compiler\AST\Expressions\ConditionalJumpExpression.cs(20,17):
error CS0234: The type or namespace name ‘Scripting’ does not exist in
the namespace ‘Microsoft’ (are you missing an assembly reference?)
Compiler\AST\Expressions\ConditionalJumpExpression.cs(22,17):
error CS0234: The type or namespace name ‘Scripting’ does not exist in
the namespace ‘Microsoft’ (are you missing an assembly reference?)

and a lot more after that.

Tomas R.:

exact same error.

Wow … this is spooky. My local version is different from what’s in SVN
right now (via the HTTP browser [1]), but I just did a clean pull from
SVN. It looks like something is messed up in a cache somewhere. Let’s
see what I can do to fix this.

Thanks,
-John

[1] http://ironruby.rubyforge.org/svn/trunk/src/ironruby/Ruby.csproj

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs