unless something fundamental in the runtime has change recently, i don't think it's so easy a fix. the problem being that you cannot reflect on a corlib other than the one being used for execution. a while ago i suggested adding support for Assembly.Load()ing multiple corlibs, but it got turned down becuse it's too hard given the current type architecture in the runtime. apparently.
piers. -----Original Message----- From: Miguel de Icaza [mailto:[EMAIL PROTECTED] Sent: Monday, March 03, 2003 9:21 PM To: Gert Driesen Cc: jopryor; mono-list Subject: Re: [Mono-list] effect of -nostdlib option Hello, > What you're actually saying is that it's not possible to use Mcs.exe on > Windows to compile an assembly using the Mono system assemblies, without > running it using the Mono runtime. > > I was hoping I could use the -nostblib option to force Mcs not to load the > MS.NET corlib. But I guess it's not possible, right ? In the MCS compiler -nostdlib turns on a special mode in which the compiler is setup for self-hosting. Since the compiler is written in C# and uses System.Reflection as its core type repository, there a number of assumptions in the code about the meaning of this flag. In reality we should three states: * Normal state. * Do not load default libraries, I will provide them in the command line * Do not load default libraries, and setup for corlib bootstrap Today -nostdlib stands for (3), while the behavior you want is (2). It is not very hard to fix, but it is a very low priority for me. If someone wants to do it, feel free to send a patch. Miguel _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
