ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ba...@goodconsultants.com
Subject Re: [Ant-contrib-developers] Problems with cc task, using libset
Date Tue, 02 Mar 2004 03:30:53 GMT
All,

More debugging trying to find out whats going on...

I just loaded with cpptasks 1.0b2.

According to the example in http://cvs.sourceforge.net/viewcvs.py/ant-
contrib/cpptasks/Attic/cc.html?rev=1.7

The following should work (right?!):

<target name="compile" depends="prepare,compile_dependencies">

        <cc name="gcc" link="${output.type}" objdir="${outlib.home}" debug="true
"
        outfile="${output.file}">

        <fileset dir="." includes="*.c"/>

        <includepath>
        <path refid="default.include"/>
        <path refid="extra.include"/>
        </includepath>

        <libset libs="pdlb">
        <fileset dir="../../build/lib"/>
        </libset>

        </cc>

</target>

But instead, I have the following errors:

BUILD FAILED
/home/barry/p4/barry/client/src/c/poliwall/pdllib/test/build.xml:51: Class net.s
f.antcontrib.cpptasks.types.LibrarySet doesn't support the nested "fileset" elem
ent.

Please help and let me know what I did wrong. If you compare this to previous 
email I sent, I have not use "libset id" here and trying to find out whats 
wrong with the build.xml. When putting "libset id" into the code and trying to 
use "libset refid", then it will result in the other error that indicate libset 
is not defined:

> [barry@fire test]$ ant
> Buildfile: build.xml
> 
> BUILD FAILED
> /home/barry/p4/barry/client/src/c/poliwall/pdllib/test/build.xml:49: Could 
not c
> reate task or type of type: libset.
> 
> Ant could not find the task or a class this task relies upon.
> 
> This is common and has a number of causes; the usual
> solutions are to read the manual pages then download and
> install needed JAR files, or fix the build file:
>  - You have misspelt 'libset'.
>    Fix: check your spelling.
>  - The task needs an external JAR file to execute
>    and this is not found at the right place in the classpath.
>    Fix: check the documentation for dependencies.
>    Fix: declare the task.
>  - The task is an Ant optional task and optional.jar is absent
>    Fix: look for optional.jar in ANT_HOME/lib, download if needed
>  - The task was not built into optional.jar as dependent
>    libraries were not found at build time.
>    Fix: look in the JAR to verify, then rebuild with the needed
>    libraries, or download a release version from apache.org
>  - The build file was written for a later version of Ant
>    Fix: upgrade to at least the latest release version of Ant
>  - The task is not an Ant core or optional task
>    and needs to be declared using <taskdef>.
> 
> Remember that for JAR files to be visible to Ant tasks implemented
> in ANT_HOME/lib, the files must be in the same directory or on the
> classpath
> 
> Please neither file bug reports on this problem, nor email the
> Ant mailing lists, until all of these causes have been explored,
> as this is not an Ant bug.




---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message