[Mono-list] effect of -nostdlib option

2003-03-02 Thread Gert Driesen
Hi,   Can anyone explain what the effect of specifying the -nostdlib option is for the Mcs (using the Mono runtime or the .NET runtime) ?   For the MS.NET compiler it allows you to specify another mscorlib.dll that should be linked instead of the .NET Framework mscorlib.dll.   But for Mcs th

Re: [Mono-list] effect of -nostdlib option

2003-03-03 Thread Gert Driesen
guess it's not possible, right ? Gert - Original Message - From: "jopryor" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]>; "mono-list" <[EMAIL PROTECTED]> Sent: Monday, March 03, 2003 6:27 PM Subject: RE: [Mono-list] effe

Re: [Mono-list] effect of -nostdlib option

2003-03-03 Thread Ian MacLean
Jon wrote: -nostdlib does two things. It keeps corlib.dll from being loaded by default. The second thing is what's causing you problems. -nostdlib tells mcs to grab all types from the files it's compiling. This includes the base types, such as System.Object (which you were getting errors abo

Re: [Mono-list] effect of -nostdlib option

2003-03-03 Thread Ian MacLean
Ian MacLean wrote: Hmm I think the second part is incorrect behaviour. if you add a reference to another corlib then it should find the types there. If you use csc.exe with the following commandline: csc -nostdlib -r:C:\mono-0.20\install\lib\corlib.dll Class1.cs it works fine. However with cs

Re: [Mono-list] effect of -nostdlib option

2003-03-03 Thread Miguel de Icaza
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 g

RE: [Mono-list] effect of -nostdlib option

2003-03-03 Thread Piers Haken
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 -

RE: [Mono-list] effect of -nostdlib option

2003-03-03 Thread Miguel de Icaza
Hello! > 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 i

RE: [Mono-list] effect of -nostdlib option

2003-03-04 Thread jopryor
-nostdlib does two things. It keeps corlib.dll from being loaded by default. The second thing is what's causing you problems. -nostdlib tells mcs to grab all types from the files it's compiling. This includes the base types, such as System.Object (which you were getting errors about). The on

RE: [Mono-list] effect of -nostdlib option

2003-03-04 Thread jopryor
x27;s not possible, right ? > >Gert > >- Original Message - >From: "jopryor" <[EMAIL PROTECTED]> >To: "Gert Driesen" <[EMAIL PROTECTED]>; "mono-list" ><[EMAIL PROTECTED]> >Sent: Monday, March 03, 2003 6:27 PM >Subject:

Re: [Mono-list] effect of -nostdlib option

2003-03-04 Thread Paolo Molaro
On 03/04/03 Miguel de Icaza wrote: > > 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 Assembl