Cloning it to the default location will allow you to
build any of the components without having to modify any
component build scripts.

NOTE: YUI Builder is also available for download as a zip from
http://yuilibrary.com/downloads. If downloading from this location
to build yui2 or yui3 source, make sure to unzip the contents into
the directory structure mentioned above, to have the build work out
of the box.

Building An Existing Component

With ANT and the YUI build infrastructure installed, you can now build any
of the components from source, using the build.xml file in the component's
source directory.

The build system allows you to build locally, within the component's
source directory, and also run a full build to update the top level build
directory for a component.

Full Build

To perform a full build for a component, run ant with the "all" target:

e.g:

prompt> cd yui2/src/autocomplete
prompt> ant all

The "all" build target will build the component from its source files AND
deploy the built files, as well as any assets, to the top level build
folder:

<project>/build/<component>

So, for autocomplete, the built files would be copied to:

yui2/build/autocomplete

NOTE: When invoking ant without a file argument, as we do above, it will
use build.xml, if present in the current directory - which is what we want.

LOCAL BUILD

To perform a local build for a component, run ant without a target:

e.g:

prompt> cd yui2/src/autocomplete
prompt> ant

This will run the default target, which is "local".

The "local" build target will build the autocomplete component from its
source files, but will NOT deploy the built files to the top level build
folder.

The locally built files are stored in the temporary directory:

<project>/src/<component>/build_tmp

So, for autocomplete, the built files can be found in the directory below:

yui2/src/autocomplete/build_tmp

Build Output

ANT will output build information to the screen, as it runs through the
build, which can be redirected to a file if required:

Further Customization

If required, you can define custom values for any of the properties
defined in builder/componentbuild/docs/properties.html to customize the
build for your new component, however as mentioned above, for most
components the properties defined in the template files should be
sufficient.

You can also override or extend existing targets, to customize the actual
build process for a component if required. The list of targets and their
role is defined in builder/componentbuild/docs/targets.html.

Log Verbosity

ant all will give you the default log output, may be a little noisy

ant all -v will give you full log output (really noisy)

ant all -q will give you only the jslint output from your build

JSLint/Hint

By default, we look for the node executable. If found we use a Node.js based
JSLint server to lint the JS files. If it's not installed, we fall back to
Rhino (which can be very slow)

If you install the jshint (npm -g i jshint), we will use that by default.

To skip using this you can pass -Djshint.skip=true:

`ant all -q -Djshint.skip=true`

The default is also to only run jslint/hint on RAW files, skipping min and debug versions.