I'm trying to build a assemby using Mono 0.20 on Windows, but apparently the Mcs task calls the mcs.exe, this will cause Mono to compile an assembly using the .NET runtime instead of the Mono runtime.
The task should instead call "mono mcs.exe [options]"I think *should* is pushing it. As a managed exe it *should* be able to run against any runtime on the system and if NAnt is already running against the .Net runtime then it seems a bit over the top to be spawning another runtime.
should be specified with a full path (eg. mono c:\mono-0.20\install\bin\mcs.exe -target:exe -out:test.exe -recurse:*.cs) or the mcs.bat file (which makes sure that mcs compiles using the Mono runtime).
Its not that simple. If you want to be using mono to run mcs then you probably want to use it to run *every* managed exe - not just mcs.exe. So maybe if you start nant with mono on windows ( mono NAnt.exe -buildfile: ... ) then every managed app that is started should be started with "mono somemanagedapp.exe ).
Apparently some of the commandline options should be changed too.
Ideally the mcsTask should go. There should be no need to have a different task for every c# compiler.
Do we wait until Ian finishes his runtime support or do we patch this right now ?
I think we should decide what the correct option is first.
Ian
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
