[MonoDevelop] Nunit configure patch
Lluis Sanchez
lluis at ximian.com
Wed Mar 29 06:49:53 EST 2006
El mié, 29-03-2006 a las 01:00 -0800, Christian Hergert escribió:
> This doesnt solve the problem. Not all distributions package the mono
> provided nunit. Debian/Ubuntu actually package the upstream nunit and
> therefore use nunit.pc.
>
> This can be fixed with the following.
>
> dnl nunit
> PKG_CHECK_MODULES(NUNIT, nunit >= 2.2.0,
> [
> NUNIT_LIBS=$NUNIT_LIBS
> ],
> [
> PKG_CHECK_MODULES(MONO_NUNIT, mono-nunit >= 1.1.9)
> NUNIT_LIBS=$MONO_NUNIT_LIBS
> ])
>
> This still leaves one issue. This only links against that specific
> nunit. You can still have runtime issues if the proper nunit lib isnt
> available, or loads another nunit, as the upstream and mono provided
> ones are typically slightly different, and suffer from separate bugs
> (at least this was the case a while back).
>
> We might just consider providing nunit in contrib and linking directly.
Using a private copy of NUnit isn't a solution either. A public release
of NUnit will still be needed to compile the nunit projects. So you'll
end up compiling your projects with the installed NUnit, and running
them with the private copy of the add-in.
I think the best we can do right now is to fix the compilation issue,
and add a dependency in the NUnit add-in to make sure it is not loaded
if nunit is not installed.
So, how should the compilation be fixed? there is a patch in
http://bugzilla.ximian.com/show_bug.cgi?id=76814. Is this good? I
already applied the patch that removes unneeded nunit references.
Lluis.
More information about the Monodevelop-list
mailing list