From: Ian M. <ia...@ac...> - 2004-01-27 01:25:07
|
The references tag should work just fine with wildcards. It could be=20 that build.bin is not being set to the value that you think it is. Of=20 course I'm just speculating based on the information you've provided.=20 Try setting basedir to the full path to your output directory as a test. also use the -v flag to see the list of matching references that gets=20 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=20 > get rid of the need for explicit references to libraries for each=20 > project. Instead what I have done is setup a folder in which all=20 > outside assemblies can be found and they get copied over to our output=20 > directory. Assuming all the libraries get compiled in the correct=20 > order, everything should be able to compile by just passing in=20 > reference to all the dlls in the current output folder. > > This is what I have tried so far, and it doesn=92t seem to work. (It=20 > doesn=92t pickup any of the dlls=85) > > <csc > > target=3D"${targettype}" > > output=3D"${build.bin}\${assembly}" > > debug=3D"${Debug}" > > verbos=3D"true" > >> > > <sources basedir=3D"${build.src}\${sourcedir}"> > > <includes name=3D"*.cs" /> > > </sources> > > <references basedir=3D"${build.bin}"> > > <includes name=3D"*.dll" /> > > </references> > > </csc> > > Of course this is going to be a temporary fix, after we sort out all=20 > of the projects I do plan on referencing them explicitly=85 > > Do you guys have any solutions? > > Chris > --=20 Ian MacLean, Developer,=20 ActiveState, a division of Sophos http://www.ActiveState.com |