Description
Runs the Nice compiler.
All arguments to the Nice compiler Task has to be placed as attributes in the nicec xml-element.
Parameters
| Attribute |
Description |
Required |
| package |
The Nice package to compile. |
Yes |
| jar |
Compile the Nice sources to archive. |
No |
| sourcepath |
Search path for source packages. Is a list of directories and .jar archives. |
No |
| destination |
Destination directory for compiled packages. |
No |
| classpath |
Search path for compiled packages and libraries. |
No |
| output |
Generate native executable. |
No |
| compile |
Compile packages but do not link them. |
No |
| recompile |
Force recompilation of package. |
No |
| recompile_all |
Force recompilation of all dependant packages. |
No |
| exclude_runtime |
Avoid inclusion of the runtime in the archive. |
No |
| runtime |
Location of nice.jar. |
Yes |
| native_compiler |
Location of the native compiler binary (gcj). |
No |
| editor |
Tell nicec that it is called by an editor. |
No |
classpath
Nicec's classpath attribute is a PATH like structure and can also be set via a nested
classpath element. This is very reasonable if you want to make your build script's pathes platform
independent.
Example
<nicec package="test" >
<classpath>
<pathelement location="\test.jar"/>
<pathelement path="${java.class.path}"/>
</classpath>
</java>
It is possible to use the classpath attribute together with the
classpath nested tag. In this case the result is a concatenated path.
It is highly recommended to use the nested version!
Examples
<taskdef name="nicec" classname="nice.tools.ant.Nicec"/>
<target name="nice-compiler">
<nicec package="test" runtime="../share/java/nice.jar"/>
</target>
author:
Alex Greif alex.greif@web.de |