ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: <csc> and Mono (was Re: cvs commit: ant/src/etc/testcases/taskdefs/optional dotnet.xml)
Date Thu, 07 Aug 2003 07:13:44 GMT
On Wed, 06 Aug 2003, Steve Loughran <> wrote:

> yup. We either want no refs, or we want the mono refs.

With /nostdlib+ and Mono refs it doesn't work (Mono tries to open the
refs in read/write mode, no idea why).  So in the case of Mono I'd
vote for no refs.

> I was thinking of something different,

As you understand the .NET area and I don't, at least not yet, please
go ahead and use me and my Linux setup as the Mono guinea pig.

> 1. drop all predefined references the moment you name an executable
> on the command line.

Won't that cause a backwards compatibility problem?

> How can I say <fileset path="${env.PATH}" includes="System.dll"/>

Similar to how <extdirs> is handled in <javac>?  I.e. add a Path
nested element and make the task create filesets from it - fall back
to env.PATH or env.Path if the user doesn't specify a path?

On Linux it doesn't seem to use PATH but either something that's
hardcoded inside of Mono or the dynamic linker architecture (as it
picks up the .dlls from /usr/lib for me).  "strings mono" doesn't give
any clues to me.  I'd probably simply have to read the documentation
to know 8-)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message