[Mono-dev] Mono Hints for Developers.

[Rafael Teixeira]

Just a small warning: This works if you are only changing the managed
bits of a library what is the case for most of the other libraries,
and most of the code in corlib, also.

Unfortunately corlib is not the best example in that sense, because it
depends on many native parts (shared structures/ internal call APIs)
inside the runtime and sometimes this means that sometimes you'ĺl need
to do a full rebuild from the native ('mono' tree) side, that keeps
things in sync. You'll receive a nice, but frustating, error message
when trying to run any program with Mono, if you compile and install a
new corlib that doesn't match the expected internal version number the
runtime was compiled for, and vice-versa.

Fun,

On 3/18/07, Miguel de Icaza <miguel at ximian.com> wrote:
> If you are developing code in the class libraries, and you want a quick
> turn around to check your changes, for example, for corlib, do this:
>
>         cd mcs/class/corlib
>         make                            ; for 1.0 profile
>         make PROFILE=net_2_0            ; for 2.0 profile
>         make install                    ; To install your 1.0 profile
>         make PROFILE=net_2_0 install    ; To install the 2.0 profile
>
> To run the tests do:
>
>         cd mcs/class/corlib
>         make run-test-local
>         make run-test-local PROFILE=net_2_0
>
> Miguel.
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>


-- 
Rafael "Monoman" Teixeira
---------------------------------------
"The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man." George Bernard Shaw