also use the -v flag to see the list of matching references that gets passed to csc.exe.
Hope this helps.
btw it looks like you have misspelt verbose as verbos.
Ian
Trudel, Chris wrote:
Our primary build consists of around 30 projects and I am trying to get rid of the need for explicit references to libraries for each project. Instead what I have done is setup a folder in which all outside assemblies can be found and they get copied over to our output directory. Assuming all the libraries get compiled in the correct order, everything should be able to compile by just passing in reference to all the dlls in the current output folder.
This is what I have tried so far, and it doesn’t seem to work. (It doesn’t pickup any of the dlls…)
<csc
target="${targettype}"
output="${build.bin}\${assembly}"
debug="${Debug}"
verbos="true"
<sources basedir="${build.src}\${sourcedir}">
<includes name="*.cs" />
</sources>
<references basedir="${build.bin}">
<includes name="*.dll" />
</references>
</csc>
Of course this is going to be a temporary fix, after we sort out all of the projects I do plan on referencing them explicitly…
Do you guys have any solutions?
Chris
--
Ian MacLean, Developer, ActiveState, a division of Sophos
http://www.ActiveState.com
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
