Gary Feldman wrote:
From: "Andy Harris" <[EMAIL PROTECTED]>
Sent: Thursday, August 26, 2004 12:59 PM
I will have target name collision if I do that. There exist a common set
...
concept of dependencies across build files. My original plan was to
have
n build files, but a build target in one is dependant on build targets
of other files. I don't see how these dependencies can be accomplished
across build files. I suppose I am back to putting all projects in one
Can't you just use the <nant> task for this? A common build setup is for
each subproject to have its own build file, and for there to be a top level
file that invokes the lower level files. By using the <nant> task, you
avoid the target name collision.
using the <nant> task you have to manage dependencies between targets
yourself. ie you need to explicitly call the child build file - you
can't declaratively say that a given target has a dependency on a
different target in another file - which is what Andy was asking for.
Ian
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
