> 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 b
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 fo
> The actual problem is that I have some top-level include file that
> contains
> stuff like:
>
>
>
>
> .
>
> I want these properties set when I include them in my build files.
> There is
> a variety of top-level directories that my build scripts will need to
> know
> about. Basically the
The actual problem is that I have some top-level include file that contains
stuff like:
.
I want these properties set when I include them in my build files. There is
a variety of top-level directories that my build scripts will need to know
about. Basically these properties need to be s
[mailto:jonathan.new...@ni.com]
Sent: Tuesday, August 18, 2009 10:03 AM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] Getting the Path of an Included Build File
I would like to create a common include file that several of my builds
use.
It would setup a few global directorise and properties. Then my
> I would like to create a common include file that several of my builds
> use.
> It would setup a few global directorise and properties. Then my build
> files
> would just use the element. However, I am trying to use the
> project::get-buildfile-path() function inside my include file to get
> the
I would like to create a common include file that several of my builds use.
It would setup a few global directorise and properties. Then my build files
would just use the element. However, I am trying to use the
project::get-buildfile-path() function inside my include file to get the
current path
