It looks like Microsoft.dynamic and IronPython also fail to build, but
xbuild tries to continue anyway.
The root cause is that msc and csc have slightly different warnings by
default, and we have warnings as errors turned on. I try to make sure mono
always builds, and I was pretty sure I had fixed
$ xbuild Solutions/IronPython.sln /p:Configuration=Release
The first errors:
array.cs(24): error CS0234: The type or namespace name `Operations'
does not exist in the namespace `IronPython.Runtime'. Are you missing
an assembly reference?
array.cs(25): error CS0234: The type or namespace name `Type
You probably want to set the configuration you want to build via
/p:Configuration=Debug /p:Platform="Any CPU" or if you want a release
version, try /p:Configuration=Release. The full solution builds a
large number of configurations which may not work to build on mono.
slide
On Wed, Apr 18, 2012
No luck with the vanilla IronPython solution file.
There is a dependency on Silverlight?
http://pastebin.com/11rZTC3F
This documentation is also out of date:
https://github.com/IronLanguages/main/wiki/Building#wiki-wiki_building-mono
On Thu, Apr 19, 2012 at 1:47 PM, Slide wrote:
> You shouldn't
You shouldn't need to use the IronPython.Mono.sln file anymore, you
should be able to use the vanilla IronPython solution file. Does that
not work for you?
Thanks,
slide
On Wed, Apr 18, 2012 at 4:16 PM, Eddy Pronk wrote:
> I'm trying to build IronPython on mono 2.10 (Debian)
>
> I followed thes
