On Wed, 03 Sep 2003, Steve Loughran <[EMAIL PROTECTED]> wrote:
> I proose, therefore, that we pull all 'helpful' auto referencing
> from the ant task because it wasnt needed on windows, and broke
> mono. Then we can get rid of that extra attribute we hacked in for
> mono support.
+1
Stefan
I've been thinking about the .net tasks and the tricks we had to do with
mono support
the underlying problem was that because the task was always explicitly
importing lots of stuff from the .net framework, the defaultreferences
attribute was overloaded.
But it turns out that the MS CSC compile
Stefan Bodewig wrote:
On 13 Aug 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
testCSCReferences fails with
[csc] error CS2001: Source file '/D:RELEASE;def3;' could not
be opened
my wild guess is, it's the trailing semicolon here as well. Will
try to verify.
OK, the trailing semi ha
On Wed, 13 Aug 2003, Martin Gainty <[EMAIL PROTECTED]> wrote:
> Could you provide the source so we can run the CSharp Compiler and
> see the errors on our own box?
I've been running ant on the build file you can find as
src/etc/testcases/taskdefs/optional/dotnet.xml using a freshly
bootstraped CV
On 13 Aug 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> testCSCReferences fails with
>
> [csc] error CS2001: Source file '/D:RELEASE;def3;' could not
> be opened
>
> my wild guess is, it's the trailing semicolon here as well. Will
> try to verify.
OK, the trailing semi has not
Stefan-
Could you provide the source so we can run the CSharp Compiler and see the
errors on our own box?
-Martin
- Original Message -
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 13, 2003 6:59 AM
Subject: .NET tasks an
I've played some more with it (see my last commit).
testCSC, testCSCintrinsicFileset and testCSCdll pass.
testCSCReferences fails with
[csc] error CS2001: Source file '/D:RELEASE;def3;' could not be opened
my wild guess is, it's the trailing semicolon here as well. Will try
to verify.
