[Mono-list] Build fails on AppDomain because of AssemblyBuilder constructor

[Paolo Molaro]

On 11/06/01 Nick Drochak wrote:
> The build is failing at AppDomain.  The error is:
> System.Reflection.Emit.AssemblyBuilder.AssemblyBuilder()' is
> inaccessible due to its protection level
> 
> I think the compiler is referencing the MS version of AssemblyBuilder to
> resolve this and thus the error. There's no constructors defined in the
> mono AssemblyBuilder, so a default public one should be provided by the
> compiler, right?
> 
> Please let us know what you did to fix this.  This seems like a great
> example to learn from.

I actually didn't do anything, since the build works fine for me (make
linux).
I tried 'make windows' and that is indeed failing, but it fails even if
I add an explicit constructor.
I see that it fails making the corlib_res.dll target, because that
excludes the Reflection.Emit/*.cs files, so it doesn't use our code.
What is that target used for? Why does it exclude so much stuff from our
corlib? Some stuff in our corlib depends on the internal implementation
and as such, you can't mix some types from our corlib and some from
mscorlib. If this is needed for testing, we should make sure the test
tool works with mint and use that to drive the test runs.
If someone comes up with a list of the needs of the testing tool that we
don't yet implement I can have a go at it.

For the time being I excluded AppDomain.cs from the corlib_res.dll
target, so that the build gets going again.

lupus

-- 
-----------------------------------------------------------------
lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better