I am planning on just using a relative path to the main include file. I'm
just trying to avoid specifiying all these properties in all of my top-level
build files. Like I have a structure like:
Trunk
ADE
ade.build
RTE
rte.build
Blah
blah.build
The ADE, RTE, Blah, etc folders are all products that can be built
independently but they all will share a variety of directory paths (i.e.
paths to build tools).
So in my ade.build file for example, I would do something like:
include buildfile="..\..\global.include" />
--
View this message in context:
http://www.nabble.com/Getting-the-Path-of-an-Included-Build-File-tp25025552p25027685.html
Sent from the NAnt - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
NAnt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nant-users
