From beb51aa385f0b9e0c5e02a4f0eae267a0958eff4 Mon Sep 17 00:00:00 2001 From: Jeremias Maerki Date: Thu, 27 Oct 2005 06:49:24 +0000 Subject: [PATCH] Fixed a small mistake and explained about where "ant" comes from. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@328813 13f79535-47bb-0310-9956-ffa450edef68 --- .../content/xdocs/trunk/compiling.xml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/src/documentation/content/xdocs/trunk/compiling.xml b/src/documentation/content/xdocs/trunk/compiling.xml index 507a93a4d..7de1278a8 100644 --- a/src/documentation/content/xdocs/trunk/compiling.xml +++ b/src/documentation/content/xdocs/trunk/compiling.xml @@ -79,6 +79,11 @@ The examples below are for running the shell script, but except for the build file extension, the syntax is identical.

+ + The "ant.bat" and "ant.sh" are only available on your system if you've properly + installed Apache Ant and added Ant's location to the PATH + environment variable. +

The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. It contains information for numerous build targets, many of which are building blocks to more @@ -104,12 +109,16 @@

To run the build:

ant.sh [target ...] -

For example to do a normal build for the "package" target (which is the default):

+

For example to do a normal build for the "all" target (which is the default):

ant.sh

OR

- ant.sh package + ant.sh all

To clean the build directory first:

- ant.sh clean package + ant.sh clean all + + If you want to shorten the build time you can just call the "package" target which + doesn't perform any automated tests during the build. +
Troubleshooting -- 2.39.5