Martin,
I still think that if you need more flexiblity, you should use the
individual compiler tasks.
Why do you need to specifiy additional args in the NAnt <solution> task that
you don't need when building using VS.NET ?
Gert
----- Original Message -----
From: "Martin Aliger" <[EMAIL PROTECTED]>
To: "'! nant'" <[EMAIL PROTECTED]>
Sent: Thursday, September 30, 2004 5:07 PM
Subject: [nant-dev] <solution> and compiler arguments
> Hello,
>
> I just tried to migrate to newest nightly of NAnt and found (again) that
I
> have to specify some custom options to csc.exe when compiling mine
projects:
>
> <solution configuration="Release" outputdir="${output.dir}"
> includevsfolders="false">
> <projects>
> <include name="*.csproj"/>
> </projects>
> <compilerargs>
> <arg value="/codepage:1250"/>
> <arg value="/nowarn:0612"/>
> <arg value="/nowarn:0618"/>
> <arg value="/nowarn:1591"/>
> <arg value="/warnaserror"/>
> </compilerargs>
> </solution>
>
> I remeber there was serious complains against this patch of mine. Maily
> because arguments are compiler and language specific. What about to
> restructure it somehow to be acceptable by community? E.g.
> <compilerargs>
> <csc>
> <arg value="/codepage:1250"/>
> </csc>
> </vbc>
> <arg value="/whatever:option"/>
> </vbc>
> </compilerargs>
>
> Martin
>
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
