I'm not sure if we really need to/should have a single binary distribution. Our current binary distribution targets .NET 1.0, while Mono is effectivily positioning itself as .NET 1.1 compliant, not 1.0. So this could potentionally cause problems to start with ...
We currently also have tasks or task assemblies that are (runtime) framework or platform specific, and we could have more of them in the future (eg. wrapper tasks for linux-specific command-line tools). If we create a single binary distribution, we should also make it clear which tasks are supported/available for which platform/framework and we should include several sets of sdk docs as not all assemblies will be available for all platforms/framework, and not all docs are readable on all platforms (I don't think its possible to read html help docs on linux) ... this will not simplify things at all ... Creating a binary distribution for each supported framework version should not be this hard, so I don't think we should rule this out ... Gert ----- Original Message ----- From: "Scott Hernandez" <[EMAIL PROTECTED]> To: "! nant" <[EMAIL PROTECTED]> Sent: Sunday, January 04, 2004 1:43 AM Subject: Re: [nant-dev] Single NAnt binary for all platforms > This a great goal. A single binary dist for all runtimes sounds great. > > +1 > > I will try to look this over at the start of the week. > > ----- Original Message ----- > From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]> > > Hi! > > > > As Mono is progressing towards 1.0, I think we should start thinking about > a > > binary distribution of NAnt that would run unmodified on all CLI > platforms. > > > > I've done some review of the NAnt source code and looks like there are no > > fundamental problems that would prevent us from achieving this soon. > > > > Here are my thoughts: > > > > 1. Some code (actually very little) is P/Invoke dependent. This code > should > > be isolated and put in one place. > > > > 2. There is one bug in Mono which requires NAnt to use conditional > > compilation to overcome the bug. Vide "_timeout" in > ExternalProgramBase.cs. > > There's no reason why this should be done at compile time. > > > > 3. Some task assemblies aren't made to work with Mono yet. Win32Tasks and > > VSNet tasks. What about <solution> task then? > > > > 4. I've tried to run mono win "log4net.dll" compiled for .NET 1.0 and it > > works fine. In fact this version should run just fine on all CLI platforms > > because NAnt doesn't use any platform specific features of log4net. > > > > 5. I'm not sure about other binaries in "lib" directory. Are there any > > limitations of mono that prevent us from using .NET 1.0 binaries on all > > platforms? The DLLs are 6 months old, I believe we've seen a huge progress > > in Mono world since then. > > > > To address issues 1 & 2 I've prepared a patch that attempts to fix the > > issues. > > > > With these fixes in place I was able to rebuild NAnt on Windows, move > > binaries to Linux (removing VSNetTasks and Win32Tasks) and rebuild NAnt > > completely on Linux without resorting to makefile. > > > > Can you review it and tell me your opinion? > > > > Jarek > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > > ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
