I don't think there's really any task like <cc> :)
There is however tasks that give you the names of
files, such as <tempfile>.  Most task though expect you
to input a filename.  However the <cc> task tries
to hide the file extensions from you (for platform
independence).  The code is really simply, and involves
only a change to the CCTask itself.  All the information
it needs is available to it already.  It's just a matter
of letting the user get to it.


----------------
Matthew Inger [inger@synygy.com]
Software Developer
Synygy, Inc
610-664-7433 x 7770
"Man who jump off cliff, leap to conclusions." - Confucious


-----Original Message-----
From: Curt Arnold [mailto:carnold@houston.rr.com]
Sent: Tuesday, August 19, 2003 12:38 AM
To: Inger, Matthew; ant-contrib-developers@lists.sourceforge.net
Subject: Re: [Ant-contrib-developers] output files from <cc> task


I'd give 24 hours to see if anybody else responds, but I don't have a
problem with it  There had been a previous request for a feature like
that, but I don't think we discussed it much.

Is there any existing task in Ant that sets a precedent for this type of
behavior?

Inger, Matthew wrote:

> PS:  I have the code change for this already.  I can check in as long
> as no one has objections:

> <cc ...

>       outputFileProperty="some.property"> ... </cc>


>
> ----------------
> Matthew Inger [inger@synygy.com]
> Software Developer
> Synygy, Inc
> 610-664-7433 x 7770
> "Man who jump off cliff, leap to conclusions." - Confucious
>
>     -----Original Message-----
>     *From:* Inger, Matthew [mailto:inger@Synygy.com]
>     *Sent:* Monday, August 18, 2003 11:22 AM
>     *To:* ant-contrib-developers@lists.sourceforge.net
>     *Subject:* [Ant-contrib-developers] output files from <cc> task
>
>     Would it be possible to have another attribute on the <cc> task which
>     would give the actual physical name of the resultant output file?
>
>     doing something like:
>
>     <cc ....
>
>            outfile="SomeLib">
>     ...
>     </cc>
>
>     yields a file such as "libSomeLib.so" or "SomeLib.dll".
>
>     Now if you want later to copy that to a distribution package, you
>     would have to know the physical filename, destroying some of that
>     type of hiding that the <cc> task is trying to accomplish.  What
>     i'd like is simply
>     a way get give <cc> a property name to set with the physical
>     filename.
>     IE:
>
>       <cc   physicalfile="output.file" ... >...</cc>
>
>       <copy file="${output.file}" todir="${dist.dir}" />
>
>
>     ----------------
>     Matthew Inger [inger@synygy.com]
>     Software Developer
>     Synygy, Inc
>     610-664-7433 x 7770
>     "Man who jump off cliff, leap to conclusions." - Confucious
>