On 14 Oct 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> Hmm, I assume adding a mint config in addition to
> NAnt.Console.exe.config.linux
I was obviously looking at an out-of-date Makefile, sorry.
Stefan
---
This SF.net email is sponsored
On Tue, 14 Oct 2003, Gert Driesen <[EMAIL PROTECTED]> wrote:
> So what we need is a way of determining that NAnt is running on Mac,
> so we can create a third "platform" for Mac...
No, what you need is a way of determining whether you can use mono or
have to fall back to mint. AFAIU mono is only
The useruntimeengine attribute itself is actually documented in the help for
the nightly builds
(http://nant.sourceforge.net/nightly/help/tasks/exectask.html), but perhaps
we should make it more clear as to what it exactly does ...
Gert
- Original Message -
From: "Met @ Uber" <[EMAIL PROT
We currently only support two diffferent platforms, namely win32 and unix.
For win32, we support .NET 1.0, .NET 1.1, .NET CF 1.0, SSCLI 1.0 and Mono
1.0, while for unix we only support the Mono framework (and Mac OsX is
considered to be unix).
For Mono on unix we've configured the runtime engine t
On Mon, 13 Oct 2003, Jaroslaw Kowalski <[EMAIL PROTECTED]> wrote:
> useruntimeengine="true"
> commandline="/repository ${resource.dir}/repository.xml />
Could that explain my Mac problems?
A boolean for useruntimeengine may not be enough for Mono support on
platforms where
Exactly. If you're on windows with ms .Net, nant knows that you don't
need to use a runtime engine. You can build using mono on windows and
then you will also get:
mono ${build.dir}/Ojb.Net.Tools.PoGen/pogen.exe
use the -verbose flag to see the actual command thats being used in each
case.
Ia
Apparently its just not documented, but the attribute itself works.
Thanks a lot. And that shouldn't break anything between OS's right?
On Mon, 2003-10-13 at 16:25, Met @ Uber wrote:
> That sounds like exactly what I need, but would you mind showing me an
> example of what your talking about? I
Use:
To: "NAnt-Devel" <[EMAIL PROTECTED]>
Sent: Monday, October 13, 2003 10:07 PM
Subject: [nant-dev] Exec Task OS Specific
> Does the exec task use 'mono' when on Linux to run programs? For
> example:
>
>commandline="/repository ${resource.dir}/repository.xml />
>
> Does that
That sounds like exactly what I need, but would you mind showing me an
example of what your talking about? I don't see it in the 'exec' tasks
documentation.
~ Matthew
On Mon, 2003-10-13 at 16:17, Gert Driesen wrote:
> nope, you should set the useruntimeengine attribute for the exec task to
> tru
nope, you should set the useruntimeengine attribute for the exec task to
true if you want that behaviour ...
Gert
- Original Message -
From: "Met @ Uber" <[EMAIL PROTECTED]>
To: "NAnt-Devel" <[EMAIL PROTECTED]>
Sent: Monday, October 13, 2003 10:07 PM
Subject: [nant-dev] Exec Task OS Spec
Does the exec task use 'mono' when on Linux to run programs? For
example:
http://sourceforge.net/supporters.php
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Dmitry and Ian,
I have found a problem with the VC support in the solution task. The
Refernces class still attempts to create a Project object when it should
use the ProjectFactory. Trying to create a Project object while passing
in a .vcproj file generates a null exception when the Project.Load()
On Fri, 10 Oct 2003, Scott Hernandez <[EMAIL PROTECTED]> wrote:
> If the Ant team had the option, now that they have been out there so
> long, I wonder if they would choose a sep. license for any reason.
I can only speak for myself, I wouldn't.
Ant has become as successful as it is for several r
On Fri, 10 Oct 2003, Matthew Mastracci <[EMAIL PROTECTED]> wrote:
> My largest concern is not that a company can use BSD-code, but
> rather add core enhancements (ie: modifications/enhancements/bug
> fixes to the core code) and keep those proprietary.
Yes, there is nothing inside a BSDish license
14 matches
Mail list logo
