Thanks for the quick response.
The command executes OK when I run on command line. When using the -v option
I get the following:
Apache Ant version 1.6.5 compiled on June 2 2005
Buildfile: build.xml
Detected Java version: 1.4 in: /usr/java/j2sdk1.4.2_09/jre
Detected OS: Linux
parsing buildfile
/home/ywillems/cvs/main/make_eazyx/src/plugins/batchman/build.xml with URI =
file:///home/ywillems/cvs/main/make_eazyx/src/plugins/batchman/build.xml
Project base dir set to: /home/ywillems/cvs/main/make_eazyx
[property] Loading Environment env.
Build sequence for target(s) `build_lib' is [init, build_lib]
Complete build sequence is [init, build_lib, ]
init:
[echo] Build of eazyx lib component started
build_lib:
[apply] Current OS is Linux
[apply] foo.c added as foo.o doesn't exist.
BUILD SUCCESSFUL
Total time: 0 seconds
There is no foo.o. I assume that the "[apply] foo.c added as foo.o doesn't
exist." is a normal log meaning that foo.c is taken into account since there
is no foo.o. As you stated in your reply it must have something to do with
the apply conditions: for some reason ant thinks that nothing must be done.
Yves
-----Original Message-----
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 2:41 AM
To: Ant Users List
Subject: Re: build successfull but apply did nothing
On 10/18/05, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> On 10/18/05, Yves Willems <[EMAIL PROTECTED]> wrote:
> > I'm trying to get a gcc apply task running but found out that it simply
> > doesn't execute the executable I specify.
> >
> I'd say it's possible you have a foo.o file in your current dir that's
> newer than foo.c.
If you run Ant with -verbose (or -debug), and my guess above is
correct, you should see messages from <apply> about the file being
up-to-date. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
