Unix is required. Only Linux has been tested, but most other versions of Unix should be okay.
Ensure you have Perl 5:
$ perl --version
Change to the directory of your working copy:
$ cd working-copy/
(If you have no working copy, see ../../contributors.xht#revision-control-system.)
Smoke test the build script:
$ votorola/a/build/build --help
If this is your first build, it will fail with an error message. The exact fix depends on the error message.
Can't locate Module.pm in @INC...
A Perl module is missing. Simply install the module, e.g. from CPAN.
unable to parse votorola/a/build/Build_config.pl: No such file or directory
A configuration file is missing. Config.pm explains the reason, and how to fix it.
When all of the dependencies are in place, the command will run to completion, and print a help message:
Usage:
build clean
build argument*
build --help | --man
Arguments:
clean Deletes all build files.
doc Builds the documentation files. Almost all of the source is
output, with only lightly filtering to exclude a few unwanted
files.
exec Builds the executables.
javadoc Builds the Java API docs.
release Builds the whole of Votorola for release. This is the default.
It is equivalent to 'build doc exec javadoc'.
Options:
--help Outputs a brief help message and exits.
--man Outputs the full manual page and exits.
--verbose
Increases the level of console output.
Build the code.
$ votorola/a/build/build
It prints out its progress. (As in the previous step, it may fail if any dependencies are missing. Simply supply the dependencies, and retry.)
release
doc
exec
(compile 90...
(jar files 144...
javadoc
(javadoc ...
The code is now built to the out_dir(), as defined in your Build_config.pl.
Run the code as instructed in the administrator's manual. But where it talks about an installation directory, substitute your out_dir().
Certain runtime options are useful during development. See for example the JAR_WRAPPER_OPT variable in this .bashrc. Verbose logging is also useful, as in this example logging.properties.