Re: [OT] Nant build script

Lübbe Onken wrote:

> You can create a Nant file for each lib and include these into the master
> build file.
>
> Like:
> ---SNIP---
> ./ext/subversion.build
> <project name="Subversion" default="svnlibs">
> <target name="svnlibs" />
> </project>
>
> ---SNIP---
> ./doc/doc.build
> <project name="doc" default="all">
> <target name="documentation" />
> </project>---SNIP---
>
> ---SNIP---
> tortoisesvn.build
> <project name="TortoiseSVN" default="all">
> <include buildfile="ext/subversion.build"/>
> <include buildfile="doc/doc.build"/>
>
> <target name="all" depends="svnlibs,documentation" />
> </project>
> ---SNIP---
>
> Haven't tried, but it should work this way. Looking at it from the project
> root, you end up with a "single" build file for everything, since all the
> other targets are included.
>
> Each subproject has got it's own build file

I already knew that we can include build files.
What I'm missing (better: what I don't quite get) is how do you set up
the build scripts so you can later do

nant docs en pdf <!-- builds the english pdf -->
nant docs en chm <!-- builds the english html help file -->
nant TSVN debug <!-- builds all libs (apr, subversion, ...) and
TortoiseSVN in debug build -->
nant installer <!-- does a release build, generates the docs and then
creates the installer -->

As far as I can see, that's not really possible to do. So in the end, we
don't have much more functionality with a nant script than with our
current batch file?

I think I may be missing something here...

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org