> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>
> > You probably want to use . It's like + fileset
handling
> > merged into one. --DD
>
> My last use of is a long time ago, but I think is used
for
> invoking an external application for _each_ file in a fileset, not for
the
> whole stuff.
> You probably want to use . It's like + fileset handling
> merged into one. --DD
My last use of is a long time ago, but I think is used for
invoking an external application for _each_ file in a fileset, not for the
whole stuff.
So that (pseudo) code
would simply do th
> From: Maurice Feskanich [mailto:[EMAIL PROTECTED]
>
> I'm guessing the user is exec'ing the linker directly. Remember, the
> exec task has no understanding of wildcards, so the asterisk needs to
be
> interpreted by a shell. Try this:
>
>
>
>
>
>
> Erskine, Chris wrote:
> > I have
I'm guessing the user is exec'ing the linker directly. Remember, the
exec task has no understanding of wildcards, so the asterisk needs to be
interpreted by a shell. Try this:
Maury
Erskine, Chris wrote:
> I have a user who is trying to use the exec task to link a program. As par
I have a user who is trying to use the exec task to link a program. As part
of the command line, he is trying to add the argument *.o to link in all of
the objects. Using does not seem to work. What is the
right way to pass in a wildcard option? This is running on a Sun box using
Ant 1.6.2
C
